From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] elogind: keyboard not released under certain conditions
Date: Fri, 05 Feb 2021 03:10:26 +0100 [thread overview]
Message-ID: <20210205021026.dnMpkhTZYgpaABms8JITMm1ado0Yguy_w7gHlLpDW78@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: 889 bytes --]
Closed issue by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/27132
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: Void 5.9.13_1 x86_64 AuthenticAMD notuptodate rFFF
* package: sway-1.5.1_1
### Expected behavior
keyboard grab released, linux console receives keypresses
### Actual behavior
keyboard still grabbed, can only shutdown via power key
### Steps to reproduce the behavior
* use `elogind` as `libseat` backend
* have `exec sway` in `.bash_profile`
* exit sway via `$mod+Shift+e` (`swaymsg exit`)
This started happening after the transition to `libseat` I believe. Would be interesting to know if this happens with other `wlroots` compositor as well.
prev parent reply other threads:[~2021-02-05 2:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 0:04 [ISSUE] sway: keyboard not released on exit " 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
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 ` ericonr [this message]
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=20210205021026.dnMpkhTZYgpaABms8JITMm1ado0Yguy_w7gHlLpDW78@z \
--to=ericonr@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).