From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sway: keyboard not released on exit under certain conditions
Date: Tue, 15 Dec 2020 00:34:21 +0100 [thread overview]
Message-ID: <20201214233421.w-kstZPfBpuzhiN2P2DBZCTGd8__swSl5nLke7H1CHc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27132@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/27132#issuecomment-744806898
Comment:
> You can probably reproduce using libseat's [simpletest](https://git.sr.ht/~kennylevinsen/seatd/tree/master/examples/simpletest/main.c) instead of running sway, by running it as `simpletest /dev/dri/card0` (first argument is the device to try to open).
You mean `exec simpletest /dev/dri/card0`? I don't reproduce it with that (can type in tty normally). Here's the output:
```
00:00:00.000 [INFO] [libseat/libseat.c:70] libseat_open_seat: Backend 'seatd' failed to open seat, skipping
00:00:00.002 [ERROR] [libseat/backend/logind.c:605] set_type: Could not set session type: Rejected send message, 2 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=1936 comm="/tmp/simpletest /dev/dri/card0 ") interface="org.freedesktop.login1.Session" member="SetType" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=1209 comm="elogind-daemon ")
00:00:00.002 [INFO] [libseat/libseat.c:67] libseat_open_seat: Seat opened with backend 'logind'
libseat_open_seat(listener: 0x7ffe83dbbf30, userdata: 0x7ffe83dbbf14) = 0x55886d2282a0
waiting for activation...
active!
libseat_open_device(backend: 0x55886d2282a0, path: /dev/dri/card0, fd: 0x7ffe83dbbf18) = 5
00:00:00.003 [ERROR] [libseat/backend/logind.c:132] close_device: Could not stat fd 5
```
the first error is due to `elogind` being outdated (doesn't have SetType), but what is the second error?
> @st3r4g Can you try the `release_control` branch of seatd? It includes the ReleaseControl call, which should do the trick for clean shutdowns at least.
Yeah that works. But still, it's an elogind bug... I should try master and report to them if it still happens.
next prev parent reply other threads:[~2020-12-14 23:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 0:04 [ISSUE] " st3r4g
2020-12-14 0:11 ` ericonr
2020-12-14 0:24 ` st3r4g
2020-12-14 9:47 ` st3r4g
2020-12-14 10:06 ` st3r4g
2020-12-14 10:09 ` st3r4g
2020-12-14 10:35 ` kennylevinsen
2020-12-14 10:55 ` kennylevinsen
2020-12-14 11:21 ` st3r4g
2020-12-14 11:25 ` st3r4g
2020-12-14 11:34 ` st3r4g
2020-12-14 11:34 ` st3r4g
2020-12-14 11:36 ` st3r4g
2020-12-14 11:36 ` st3r4g
2020-12-14 11:37 ` kennylevinsen
2020-12-14 11:55 ` kennylevinsen
2020-12-14 12:03 ` st3r4g
2020-12-14 12:03 ` st3r4g
2020-12-14 12:05 ` st3r4g
2020-12-14 12:06 ` st3r4g
2020-12-14 12:11 ` kennylevinsen
2020-12-14 22:22 ` kennylevinsen
2020-12-14 22:24 ` kennylevinsen
2020-12-14 22:44 ` kennylevinsen
2020-12-14 23:34 ` st3r4g [this message]
2020-12-14 23:36 ` st3r4g
2020-12-15 13:31 ` kennylevinsen
2020-12-15 13:31 ` kennylevinsen
2020-12-16 10:40 ` st3r4g
2020-12-16 10:41 ` st3r4g
2021-02-05 2:10 ` [ISSUE] [CLOSED] elogind: keyboard not released " ericonr
2021-02-05 2:10 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201214233421.w-kstZPfBpuzhiN2P2DBZCTGd8__swSl5nLke7H1CHc@z \
--to=st3r4g@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).