From: kennylevinsen <kennylevinsen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sway: keyboard not released on exit under certain conditions
Date: Mon, 14 Dec 2020 12:37:28 +0100 [thread overview]
Message-ID: <20201214113728.X0rvy3NlwPs4-Nv3k15x9-EAZdFAxV52TpYTfvCSP2I@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: 1248 bytes --]
New comment by kennylevinsen on void-packages repository
https://github.com/void-linux/void-packages/issues/27132#issuecomment-744382307
Comment:
> From the dbus trace, the difference seems to be that the logind backend calls ReleaseControl while the libseat backend does not.
ReleaseControl is indeed not called on libseat shutdown, because disconnecting from the bus is supposed to have the same effect. In elogind, this is set up here: https://github.com/elogind/elogind/blob/80c3df891cbe3bcdd27ada05ee7ca938a2c051ca/src/login/logind-session.c#L1521, with on_bus_track closing the session.
While we could just add the ReleaseControl call to libseat, not having working disconnect cleanup in elogind will lead to other problems, with e.g. a compositor crash still leaving you with a broken console.
> How are you starting sway? It happens when starting with exec sway in .bash_profile, but now manually in the shell.
Ran `LIBSEAT_BACKEND=logind sway -c sway_config -d 2>swaylog` from an empty TTY. The config is a mostly empty debug config, the env var is to force the logind backend instead of seatd.
It is very peculiar if it doesn't happen when you run it manually. I have not tried to mess around with my shell init scripts.
next prev parent reply other threads:[~2020-12-14 11:37 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 [this message]
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
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=20201214113728.X0rvy3NlwPs4-Nv3k15x9-EAZdFAxV52TpYTfvCSP2I@z \
--to=kennylevinsen@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).