If you want to be 100% sure, run `DISPLAY=:1 setxkbmap us; DISPLAY=:1
setxkbmap de; DISPLAY=:1 setxkbmap us`. If afterwards it still doesn’t
work, chances are very high that it is NOT an i3 bug.
See xinput(1) for your input devices.
On Wed, Nov 11, 2015 at 2:55 AM, Benjamin Kaiser
wrote:
> Okay
Okay I tried with `DISPLAY=:1 setxkbmap us` (wasn't 100% if us was what I
wanted, it didn't print an error when I ran it) and then changed back to
TTY2 (where i3 was loaded) and the keyboard was still unresponsive.
And yes I meant DISPLAY, that's what I typed, I just copied it out wrong in
the ema
On Sun, Nov 8, 2015 at 6:01 AM, Benjamin Kaiser
wrote:
> So the issue popped up again, these were the steps I did to debug it:
>
> - jump to TTY3
> - run: `DISAPLY=:1 setxkbmap | tee /tmp/setxkbmap.out` (not sure if I
> should have been passing any arguments specifically)
>
I meant using e.g. “s
So the issue popped up again, these were the steps I did to debug it:
- jump to TTY3
- run: `DISAPLY=:1 setxkbmap | tee /tmp/setxkbmap.out` (not sure if I
should have been passing any arguments specifically)
- observe there was no output
- jump back to TTY2, keyboard/keybindings still unresponsive
Thanks for the reply Michael,
I had the issue happen again yesterday and ran `sudo
libinput-debug-events`, then changed back to i3, run a bunch of shortcuts
and pressed a bunch of keys (all of which did nothing) then changed back to
the tty only to see that it was registering those keys being pres
When this situation happens:
1. Does running xev(1) still show keyboard events?
2. Does using setxkbmap to set your layout make the problem go away? That
should force i3 to re-grab all keys.
On Fri, Oct 30, 2015 at 12:38 PM, Benjamin Kaiser wrote:
> Hello,
>
> I've got a really weird issue tha
