Arch Linux

forGGe

Member

From: Ukraine

Registered: 2014-06-12

Posts: 14

[SOLVED] Awesome WM: shortcuts doesn't work after suspend

Hi everyone! I hit strange bug recently after (probably) upgrading my awesome wm. After suspending and then restoring my session I can't operate over already running application using Awesome hotkeys.

I have created a bug report: https://github.com/awesomeWM/awesome/issues/659 but may be Arch users experienced it as well, so I'm opening thread here as well.

Environment:
Awesome v. 3.5.7-1 , fresh rc.lua
Xorg-server v. 1.18.0-4

uname -a
Linux Host 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux

Steps to reproduce:

• open any amount of applications in awesome wm

• make sure your Mod+Shift+C combination closes a window

• suspend your PC

• restore PC

• try to close a window using shortcut, it is no longer works.

• few more hotkeys doesn't work either (like minimizing, changing geometry, etc.)

More fun:

• open new application

• you can now close its window using Mod+Shift+C

Here is what xev shows me, when I'm trying to kill it and it still lives:

KeyPress event, serial 35, synthetic NO, window 0x2600001,
    root 0xd5, subw 0x0, time 56186826, (164,47), root:(1031,717),
    state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 35, synthetic NO, window 0x2600001,
    root 0xd5, subw 0x0, time 56187430, (164,47), root:(1031,717),
    state 0x40, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 35, synthetic NO, window 0x2600001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 35, synthetic NO, window 0x2600001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 35, synthetic NO, window 0x2600001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 35, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   4   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 35, synthetic NO, window 0x2600001,
    root 0xd5, subw 0x0, time 56192388, (164,47), root:(1031,717),
    state 0x41, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x2600001,
    root 0xd5, subw 0x0, time 56192798, (164,47), root:(1031,717),
    state 0x40, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

In contrast, freshly launched xev can be closed and shows this log:

KeyPress event, serial 33, synthetic NO, window 0x2000001,
    root 0xd5, subw 0x0, time 56258125, (76,124), root:(1623,144),
    state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x2000001,
    root 0xd5, subw 0x0, time 56258303, (76,124), root:(1623,144),
    state 0x40, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

ClientMessage event, serial 33, synthetic YES, window 0x2000001,
    message_type 0x18e (WM_PROTOCOLS), format 32, message 0x18f (WM_DELETE_WINDOW)

Please let me know if more information is required, I will gladly post it here.

Last edited by forGGe (2016-02-01 12:59:38)

---

You play, you pay, you bastard.

forGGe

Member

From: Ukraine

Registered: 2014-06-12

Posts: 14

Re: [SOLVED] Awesome WM: shortcuts doesn't work after suspend

According to author of the awesome, bus is fixed in 3.5.8 - https://github.com/awesomeWM/awesome/is … -177861921

---

You play, you pay, you bastard.