Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
$mod+Shift+q stopped working #3596
I'm submitting a…
[x] Bug [ ] Feature Request [ ] Documentation Request [ ] Other (Please describe in detail)
$mod+Shift+Q has stopped working. Only $mod+Shift+Q has stopped working. It was working until yesterday, and I'm not aware of anything that's changed (no i3 upgrade, no new applications running that might be grabbing the key), but of course I can't rule that entirely out.
If I remap kill to, say, $mod+Shift+X, then it works. If I map $mod+Shift+Q to something like "exec /usr/bin/termite", then it also does not work. $mod+Shift+R does work, as do all other $mod+Shift combos I've tried, so I'm pretty sure this is unrelated to #2418 or #2417.
I have a dump from
Interestingly, xev shows no output on the
Oh, and, yes, the
I'd expect i3 to be able to capture and respond to
See above -- I haven't changed anything; I run i3, and
Binary i3 version: 4.16 (2018-11-04) © 2009 Michael Stapelberg and contributors Running i3 version: 4.16 (2018-11-04) (pid 879)to abort…) Loaded i3 config: /home/ser/.i3/config (Last modified: Sat 19 Jan 2019 09:52:01 AM CST, 933 seconds ago) The i3 binary you just called: /usr/bin/i3 The i3 binary you are running: i3
-` ser@sting .o+` --------- `ooo/ OS: Arch Linux x86_64 `+oooo: Host: XPS 13 9343 `+oooooo: Kernel: 4.20.0-arch1-1-ARCH -+oooooo+: Uptime: 48 mins `/:-:++oooo+: Packages: 2310 (pacman) `/++++/+++++++: Shell: zsh 5.6.2 `/++++++++++++++: Resolution: 1920x1080 `/+++ooooooooooooo/` WM: i3 ./ooosssso++osssssso+` Theme: GnomishDark [GTK2/3] .oossssso-````/ossssss+` Icons: AwOken [GTK2], Potenza-Dark [GTK3] -osssssso. :ssssssso. Terminal: tmux :osssssss/ osssso+++. CPU: Intel i5-5200U (4) @ 2.700GHz /ossssssss/ +ssssooo/- GPU: Intel HD Graphics 5500 `/ossssso+/:- -:/+osssso+- Memory: 1769MiB / 7880MiB `+sso+:-` `.-/+oso: `++:. `-/+/ .` `/
I do use a composer, but I've killed it during submission of this bug because frequent restarts of i3 was causing it to freak a bit out.