You are not logged in.
Upon pressing any of the XF86* keys on my laptop, I3 seems to no longer respond to shortcuts, nor do other things like text selection with mouse work. These keys are not mapped by any software, nor can I find anything relevant in my Xorg log. Here is an excerpt from Xev
KeyPress event, serial 34, synthetic NO, window 0x1000001,
root 0x55c, subw 0x0, time 6976342, (-9,410), root:(720,450),
state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x1000001,
root 0x55c, subw 0x0, time 6976438, (-9,410), root:(720,450),
state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x1000001,
root 0x55c, subw 0x0, time 6978998, (-9,410), root:(720,450),
state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 34, synthetic NO, window 0x1000001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 34, synthetic NO, window 0x1000001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 100 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
32 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 34, synthetic NO, window 0x1000001,
root 0x55c, subw 0x0, time 6979830, (-9,410), root:(720,450),
state 0x40, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: FalseAfter the `XF86MonBrightnessDown` key-release event, things are broken. The following data is from pressing `Super_L + F`, which should launch Firefox, although it does nothing. Please let me know if I can provide any further info.
Last edited by waffle0007 (2023-12-08 20:55:16)
Offline
I'm gonna say the key somehow™ crashes your shortcut dameon.
1. do you bind them in i3 directly or eg. xbindkeys
2. does the i3 process actually survive pressing that key (you could switch to a different TTY and test "ps aux | grep i3")
Online
Sorry, "crash" may be a bit of an exaggeration; i3 is still running upon triggering the XF86 keys. As far as I'm aware, the keys are not bound by anything. I don't reference them in my i3 config, and don't have xbindkeys installed, although the behaviour is the same when I do try to map them through i3.
Offline
How do you know i3 is still running (is it maybe sigstop'd) by
I3 seems to no longer respond to shortcuts
and unless you inspected the process list?
The following data is from pressing `Super_L + F`, which should launch Firefox
The shortcut /is/ intercepted (the xev pattern is that of a passive grab), so what doesn't work is to run FF, but it's currently not clear whether the failure is to spawn the process (journal? coredumps?) or the window (b/c i3 isn't mapping it)
=> Check the process tree after pressing such key, look out for FF processes and the state of I3
Online
From another tty, i3 appears to be still running after triggering the problematic keys
jack 8172 0.1 0.2 279188 21936 tty1 T 00:18 0:00 /usr/bin/i3
jack 8176 0.0 0.0 3144 640 tty1 T 00:18 0:00 dbus-launch --exit-with-session /usr/bin/i3
jack 9010 0.0 0.0 8632 6016 pts/0 S+ 00:19 0:00 rg i3Here is Xorg log. There's nothing relevant in dmesg, but let me know if I can provide additional logs. Thanks :^)
Offline
Do you know what the "T" means?
pkill -SIGCONT i3dbus-launch --exit-with-session /usr/bin/i3
Why is that there? Don't dbus-launch anything!
How do you start the session? xinit/startx? => [edit: last] link below, and post your xinitrc.
Last edited by seth (2023-12-07 07:57:48)
Online
I did not know what the T means in `ps` output... thank you for pointing that out. My current xinitrc after removing dbus-launch is
#!/bin/sh
/home/jack/.config/fehbg &
exec /usr/bin/i3and I launch X via `.zshrc`:
if [ "$(tty)" = "/dev/tty1" ]; then
exec startx
fiOffline
My current xinitrc
last link below
Pay attention to the paragraph that tells you what to at least include there.
Then report back if the process still stops.
Online
I should have tested before posting my previous message. Removing `dbus-launch ...` fixed the problem! Thank you so much for your help ![]()
Offline
Still fix your xinitc, though - otherwise you're running a degraded session.
Online