Score:0

Ubuntu 20.04 hibernates after connecting/disconnecting a keyboard

br flag

I have had ubuntu 20.04LTS on my laptop for a long time already and didn't encounter any major problems before. Today I just got my new keyboard, and when I connect it to the laptop or disconnect it from it, ubuntu goes to hibernation. Even when the keyboard is connected wirelessly, and I connect/disconnect a charging cable to it, the system reacts by going into hibernation mode. If the keyboard and mouse were connected through a USB hub, after waking the system up, they both do not work until reboot. If they were connected directly to the laptops USB ports, they work after waking up normally. Did someone encounter a similar issue? Googling didn't help much. Any advice will be very much appreciated.


System info:

  • Laptop Mechrevo X10Ti-S
  • Intel Core i7-10875H
  • Nvidia GeForce RTX 2070 Super
  • 32GB RAM Ubuntu
  • 20.04.3 LTS Kernel 5.11.0-46-generic
  • keyboard ASUS ROG Claymore 2

Update: Just noticed these messages in syslog in the moment of connecting the keyboard:

Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 12 12:56:53 lexach91-X10Ti-S NetworkManager[1702]: <info>  [1641963413.6412] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 12 12:56:53 lexach91-X10Ti-S NetworkManager[1702]: <info>  [1641963413.6413] device (enp61s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 12 12:56:53 lexach91-X10Ti-S ModemManager[1880]: <info>  [sleep-monitor] system is about to suspend
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[2667]: Screen lock is locked down, not locking
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Jan 12 12:56:53 lexach91-X10Ti-S NetworkManager[1702]: <info>  [1641963413.6504] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 12 12:56:53 lexach91-X10Ti-S NetworkManager[1702]: <info>  [1641963413.6506] manager: NetworkManager state is now ASLEEP
Jan 12 12:56:53 lexach91-X10Ti-S NetworkManager[1702]: <info>  [1641963413.6507] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 12 12:56:53 lexach91-X10Ti-S deja-dup-monito[7367]: Source ID 488 was not found when attempting to remove it
Jan 12 12:56:53 lexach91-X10Ti-S whoopsie[2698]: [12:56:53] offline
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Source ID 33071 was not found when attempting to remove it
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: Source ID 33085 was not found when attempting to remove it
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164369'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164370'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164371'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164372'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164373'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164374'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164375'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164376'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164377'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164378'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164379'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164380'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: ../../../gobject/gsignal.c:2736: instance '0x55e86d302120' has no handler with id '164381'
Jan 12 12:56:53 lexach91-X10Ti-S gnome-shell[3701]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed

After that, the system went to sleep first and then, after logging back in, hibernated


Update 2: Checked the keyboard on 3 other machines. Windows 10 and 11 work absolutely fine with it. My wife's laptop that runs ubuntu 21.10 also going to sleep mode after connecting the keyboard. Need help guys. How to fix it? Where to look at least?

in flag
There’s almost no actionable information here, which may be why Google was also unable to assist. Brands and model numbers will go a long way to supplying answers
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.