#StackBounty: #debian #i3 #x2go i3-status freezes

Bounty: 50

I’m running i3 windows manager on Debian 10 and I’m connecting to the computer through X2go as I’m working at home at the moment.

Since the upgrade from Debian 9 to Debian 10 (done recently) the i3-status bar freezes and I have to ‘reload’ i3 which is a slight pain.

Here is my .i3status.conf

general {
    interval        = 1
    colors          = true
    color_good      = '#88b090'
    color_degraded  = '#ccdc90'
    color_bad       = '#e89393'
}

# order += "volume master"
# order += "disk /"
# order += "disk /home"
# order += "disk /media/data"
# order += "ethernet br0"
# order += "cpu_temperature 0"
# order += "memory"
# order += "load"
order += "tztime local"

# ethernet br0 {
#     #if you use %speed, i3status requires root privileges
#     format_up = "%ip (%speed)"
#     format_down = ""
# }

tztime local {
    format = "%A %e.%B %H:%M:%S"
}

# load {
#     format = "%1min"
# }

# cpu_usage {
#     format = "%usage"
# }

# cpu_temperature 0 {
#   format = "%degrees°C"
# }

# disk "/" {
#   format = "/ %avail"
#   prefix_type = custom
# }

# disk "/home" {
#   format = "/home %avail"
#   prefix_type = custom
# }

# disk "/media/data" {
#   format = "/media/data %avail"
#   prefix_type = custom
# }

# volume master {
#     format = "VOL: %volume "
#     format_muted = "MUTE "
#     device = "default"
#     mixer = "Master"
#     mixer_idx = 0
# }

When it freezes the time isn’t moving but I can still see the date and time just in a frozen state.

I’ve tried running i3status in a terminal and it’s been running fine for a few weeks non-stop;

Here is the output (note this is when I had all my settings on in my config and I haven’t had to restart it since);

 ~ % i3status
i3status: trying to auto-detect output_format setting
i3status: auto-detected "term"
/ 6.5 GB | /home 103.1 GB | /media/data 543.9 GB | 4.29 | Monday 28.September 09:10:16

I cannot replicate the problem but I think it might have something to do with when I exit X2go. When I exit X2go I keep the session running in the background, then the next day I connect to it. Now when it’s in this state is when it typically freezes. Maybe i3-status doesn’t like to be in an X2go session which has been detached but still running.


Get this bounty!!!

#StackBounty: #ubuntu #multi-monitor #i3 #wine #steam How to allow cursor to not become confined to one monitor in global fullscreen mo…

Bounty: 100

I am running i3wm on Ubuntu 20.04. When playing games on Steam, I’m trying to utilize both of my monitors. I use Proton which, in turn, uses WINE to run Windows games. Some games scale appropriately when entering fullscreen global mode in i3 but confine my mouse to the monitor in which the app originally launched.

I have tried using wine-cfg to disable capturing the mouse in fullscreen mode or emulate a virtual desktop of the appropriate size, but have had no success.

I’m beginning to think this is an i3wm issue rather than a WINE issue. Any help is appreciated.


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!

#StackBounty: #x11 #keyboard-shortcuts #kernel-modules #i3 #asus How to prevent XF86RFKill keypress from enabling Linux's airplane …

Bounty: 50

I am running Kubuntu 19.10(KDE + i3wm) on my ASUS FX505DT.

The issue

I am able to bind the XF86RFKill key using i3wm’s bindsym but this binding doesn’t seem to nullify’s Linux’s in-built binding which toggles Airplane Mode.

Behaviour of the issue

This is what xev returns when I press Fn+F12, which is supposed to trigger XF86RFKill:

MappingNotify event, serial 48, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 48, synthetic NO, window 0x7a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 48, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

While I was testing various things out, I found that my laptop has a separate input device for this function key, as shown by xinput list:

$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Mouse               id=12   [slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:30BA Touchpad            id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Asus Wireless Radio Control               id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ Power Button                              id=9    [slave  keyboard (3)]
    ↳ Sleep Button                              id=10   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD           id=11   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=14   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=15   [slave  keyboard (3)]

I further confirmed this by pressing Fn+F12 during xinput test 7 command, which got registered properly:

$ xinput test 7
key press   255 
key release 255 
key press   255 
key release 255 

What I want

I want to shift the key binding of Fn+F12 key, or XF86RFKill from Linux to i3wm. I have the script for toggling airplane mode, and I’ve bound it using:

bindsym XF86RFKill exec --no-startup-id toggle-airplane

The i3 binding works, but the issue is that, **both Linux and i3wm toggle airplane mode when the key is pressed, hence resulting in doing nothing, due to two successive toggles.

The current Airplane Mode, implemented by KDE, is actually buggy since it doesn’t remember the devices turned off before turning on Airplane Mode, and hence it turns on all the radio devices, even though they were initially turned off, after disabling Airplane Mode. I wrote a bash script to attain my goal, and hence the motivation for binding this key manually.

Update 1:

After doing some research and exploring, I’ve found that asus_wireless kernel module is responsibe for this behaviour. Simply blacklisting the module works but my laptop doesn’t detect the keypress anymore. Is it possible to somehow retain the keypress disabling the hotkey?


Get this bounty!!!