Ubuntu
linux package

"Power off" dialog appears when any three keyboard keys are pressed quickly

Bug #1926527 reported by Pedro on 2021-04-28

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language.

I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds.

It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does.

This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop.

Of course, this renders the system unusable for me.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: pete 1570 F.... pulseaudio
/dev/snd/controlC2: pete 1570 F.... pulseaudio
/dev/snd/controlC1: pete 1570 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-04-28 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
RelatedPackageVersions:
linux-restricted-modules-5.11.0-16-generic N/A
linux-backports-modules-5.11.0-16-generic N/A
linux-firmware 1.197
Tags: wayland-session hirsute
Uname: Linux 5.11.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/30/2020
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G713QR.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G713QR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.41
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G713QR_G713QR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: pete 1570 F.... pulseaudio
/dev/snd/controlC2: pete 1570 F.... pulseaudio
/dev/snd/controlC1: pete 1570 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-04-28 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
RelatedPackageVersions:
linux-restricted-modules-5.11.0-16-generic N/A
linux-backports-modules-5.11.0-16-generic N/A
linux-firmware 1.197
Tags: wayland-session hirsute
Uname: Linux 5.11.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/30/2020
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G713QR.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G713QR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.41
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G713QR_G713QR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

See original description

Tags:

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-28:

power_off.png Edit (514.5 KiB, image/png)

Revision history for this message

Chris Guiver (guiverc) wrote on 2021-04-29:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1926527

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects:

ubuntu → linux (Ubuntu)

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2021-04-29: Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1926527

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: AlsaInfo.txt

AlsaInfo.txt Edit (46.6 KiB, text/plain)

apport information

tags:	added: apport-collected hirsute wayland-session
description:	updated

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: CRDA.txt

CRDA.txt Edit (2.8 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: CurrentDmesg.txt

CurrentDmesg.txt Edit (244.0 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: IwConfig.txt

IwConfig.txt Edit (247 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lspci.txt

Lspci.txt Edit (19.3 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lspci-vt.txt

Lspci-vt.txt Edit (2.2 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lsusb.txt

#10

Lsusb.txt Edit (449 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lsusb-t.txt

#11

Lsusb-t.txt Edit (631 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lsusb-v.txt

#12

Lsusb-v.txt Edit (21.5 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: PaInfo.txt

#13

PaInfo.txt Edit (87.0 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcCpuinfo.txt

#14

ProcCpuinfo.txt Edit (24.2 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcCpuinfoMinimal.txt

#15

ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcInterrupts.txt

#16

ProcInterrupts.txt Edit (24.8 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcModules.txt

#17

ProcModules.txt Edit (6.4 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: PulseList.txt

#18

PulseList.txt Edit (22.1 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: RfKill.txt

#19

RfKill.txt Edit (112 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: UdevDb.txt

#20

UdevDb.txt Edit (235.2 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: WifiSyslog.txt

#21

WifiSyslog.txt Edit (889.7 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: acpidump.txt

#22

acpidump.txt Edit (1019.1 KiB, text/plain)

apport information

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: AlsaInfo.txt

#23

AlsaInfo.txt Edit (46.6 KiB, text/plain)

apport information

description:

updated

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: CRDA.txt

#24

CRDA.txt Edit (2.8 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: CurrentDmesg.txt

#25

CurrentDmesg.txt Edit (262.9 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: IwConfig.txt

#26

IwConfig.txt Edit (247 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lspci.txt

#27

Lspci.txt Edit (19.3 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lspci-vt.txt

#28

Lspci-vt.txt Edit (2.2 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lsusb.txt

#29

Lsusb.txt Edit (449 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lsusb-t.txt

#30

Lsusb-t.txt Edit (631 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: Lsusb-v.txt

#31

Lsusb-v.txt Edit (21.5 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: PaInfo.txt

#32

PaInfo.txt Edit (87.0 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcCpuinfo.txt

#33

ProcCpuinfo.txt Edit (24.2 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcCpuinfoMinimal.txt

#34

ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcInterrupts.txt

#35

ProcInterrupts.txt Edit (24.8 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: ProcModules.txt

#36

ProcModules.txt Edit (6.4 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: PulseList.txt

#37

PulseList.txt Edit (22.1 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: RfKill.txt

#38

RfKill.txt Edit (112 bytes, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: UdevDb.txt

#39

UdevDb.txt Edit (235.2 KiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: WifiSyslog.txt

#40

WifiSyslog.txt Edit (1.6 MiB, text/plain)

apport information

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-29: acpidump.txt

#41

acpidump.txt Edit (1019.1 KiB, text/plain)

apport information

Revision history for this message

Alex Hung (alexhung) wrote on 2021-04-30:

#42

You can run "sudo showkey" to monitor what keys are generated. When I press my power button keycode 116 press and release are generated (see keycode # on https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h).

$ sudo showkey
kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...
keycode 116 press
keycode 116 release

Similarly, run "acpi_listen" to check whether power button events are generated, ex.

$ acpi_listen
button/power PBTN 00000080 00000000
button/power LNXPWRBN:00 00000080 00000003

If you are seeing both keycode and acpi power button events when typing "off" or "any", it can be the fault of the system BIOS.

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-30:

#43

Thank you, Alex.

I just checked, and yes, I can see both "keycode 116 press/release" and "button/power PBTN 00000080 00000000 K" events.

I had 20.10 installed before 21.04, and I'd swear it didn't have this problem. I can reinstall 20.10 and confirm this later.

Just in case it's relevant in order to confirm or discard a faulty BIOS, I also have Windows 10 installed, and this problem isn't showing there.

Again, thank you for your help.

Revision history for this message

Pedro (berzasnon) wrote on 2021-04-30:

#44

No need to reinstall after all.

In the live USB of 21.04 the bug is present as described. In the live USB of 20.10 and 20.04, it isn't.

So, whatever it is, it's in 21.04, but not in 20.10 or 20.04. I guess this rules out a faulty BIOS.

Revision history for this message

Alex Hung (alexhung) wrote on 2021-05-01:

#45

It is possible udev rules are broken. You might be able to identify source of this power button events by checking keyboard scancode (with evtest) and/or workaround this by removing the power button assignment or assigning it to something else

== get scancode ==
* run "sudo apt install evtes"
* run "evtest" and select your keyboard
* try to duplicate your issue
* identify the trigger of the power button

== Modify keymap ==
* cd /lib/udev/hwdb.d/
* edit keymap file (60-keyboard.hwdb)
* add a change, ex KEYBOARD_KEY_81=f20 # mic mute
* run "sudo udevadm hwdb --update"
* reboot

There are some online examples for modifying hwdb files such as https://askubuntu.com/questions/499252/my-custom-udev-hwdb-rule-doesnt-work