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 11:35:09 +0100 [thread overview]
Message-ID: <20201214103509.Wjx5M-CTpi4QmCYJd4lE8QPXyf2qairG8fRyH8Uvwts@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: 587 bytes --]
New comment by kennylevinsen on void-packages repository
https://github.com/void-linux/void-packages/issues/27132#issuecomment-744348052
Comment:
If you drop back to the kernel console but do not have working keyboard input, then it would seem that elogind is not resetting the kernel keyboard mode (with KDSKBMODE) back to K_UNICODE. It is supposed to do this when the session control is either explicitly or implicitly dropped.
What version of elogind was tested against? You could use `busctl monitor` to get a dbus trace and compare with libseat to bare wlroots logind backend.
next prev parent reply other threads:[~2020-12-14 10:35 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 [this message]
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
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 ` elogind: keyboard not released " ericonr
2021-02-05 2:10 ` [ISSUE] [CLOSED] " 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=20201214103509.Wjx5M-CTpi4QmCYJd4lE8QPXyf2qairG8fRyH8Uvwts@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).