Score:1

How do I stop my ROG Falchion wireless keyboard from rebooting Ubuntu?

fr flag

I have recently purchased a ROG Falchion RGB wireless keyboard for use with my dual boot desktop (Win 10/Ubuntu 21.04). In Windows, using Armoury Crate, I have configured the lighting and set the power options for the keyboard to sleep after 2 minutes of idle time. What I have found is, when using Ubuntu, after the idle time has expired, instead of the keyboard going to sleep, the entire system goes into hibernation and the OS will restart unless you wake it and cancel the reboot. Currently, the only option to resolve the issue is to turn off the keyboard's power saving options in Armoury Crate. As this is not ideal, does anyone have any advice or thoughts on keeping power saving options on without causing the shutdown issues in Ubuntu?

fr flag
That's a very strange problem, indeed. Sadly, there is no official support for Aura functionality on any Linux distribution right now besides a couple open-source alternatives and none of them directly manage power options. Your best bet right now would be to turn off the power saving options until better support is introduced into Xmodmap. A similar problem happens on ROG laptopts as well: https://www.linux.org/threads/keyboard-issues-with-asus-rog.34151/
sdk777 avatar
fr flag
Thanks @AlexandreTeles. Turning off the power saving options seems to be the only way for now. I also found out if you turn off the keyboard with its on/off switch on the back, it will immediately trigger an OS shutdown.
user66081 avatar
cn flag
I landed here because on Ubuntu, when the keyboards goes to sleep, it puts the machine to sleep as well. So funny.
Score:1
cl flag

Disabling the xinput ID worked fine for me, too. However, the ID can change in certain situations, so I wrote a script to determine the correct ID before disabling it:

#!/bin/bash
IDENTIFIER="ASUSTeK ROG FALCHION System Control"

LINE=$(xinput list | grep "$IDENTIFIER")
ID=$(echo ${LINE#*id=} | tr '\t' ' ' | cut -d ' ' -f1)

if [ -n "$ID" ]; then
    xinput disable $ID
    echo "Disabled xinput ID $ID ($IDENTIFIER)"
else
    echo "No xinput ID for '$IDENTIFIER' found."
fi
Score:0
fr flag

Issue resolved. ran the following:

#xinput disable XX

XX being the device id related to 'ASUSTeK ROG FALCHION System Control'

Also, created a startup script with this line

Score:0
cn flag

For a more permanent solution, append the following config to /usr/share/X11/xorg.conf.d/40-libinput.conf:

Section "InputClass"
    Identifier         "disable asus falchioh sys control"
    MatchIsKeyboard    "on"
    MatchProduct       "ASUSTeK ROG FALCHION System Control"
    Option             "Ignore" "on"
EndSection
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.