New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

$mod+Shift+q stopped working #3596

Open
serussell opened this Issue Jan 19, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@serussell
Copy link

serussell commented Jan 19, 2019

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

$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 xdotool key "XF86LogGrabInfo", but to be honest I'm not sure how to interpret the output to find what's listening for $mod+Shift+Q. I've remapped caps lock to Super_L and set mod4 to that.

Interestingly, xev shows no output on the q press of $mod+Shift+q. I get the mod, and the shift, but denada for q. I've never seen that before. It does register c in $mod+Shift+c, but i3 doesn't reload the config so I don't know what's going on there; probably unrelated.

Oh, and, yes, the q key works fine everywhere else.

Expected Behavior

I'd expect i3 to be able to capture and respond to $mod+Shift+q.

Reproduction Instructions

See above -- I haven't changed anything; I run i3, and $mod+Shift+q doesn't work.

Environment

Output of i3 --moreversion 2>&-:

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.

@i3bot i3bot added the bug label Jan 19, 2019

@i3bot

This comment has been minimized.

Copy link

i3bot commented Jan 19, 2019

I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

@serussell

This comment has been minimized.

Copy link
Author

serussell commented Jan 19, 2019

I didn't, bot; the instructions said the logs were optional, and I wasn't sure whether -- since xev wasn't even registering the q, it would be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment