Mouse and keyboard delay or system freeze on boot with DM.

habit · 2022-12-25 15:09:29

During the boot process GDM shows me login screen, but I have to wait couple of seconds to use it - mouse and keyboard seems not loaded, or maybe system is stalled or freezed fot this time, mouse point need time to respond (keyboard too).
How to fix it and get rid of this issue? Or does my system boot too fast?
Thank you.

Almehdin · 2022-12-25 16:44:31

You could perhaps try to put an early mkinitcpio hook for keyboard? And then

mkinitcpio -p linux

after that is done.

More info at: https://wiki.archlinux.org/title/Mkinitcpio#Build_hooks

habit · 2022-12-25 17:04:03

I have line

HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems fsck)

at /etc/mkinitcpio.conf file.
Does this mean I have allready keyboard hook?
I have read HOOKS part from wiki, but there isn't clear how to enable them or disable. Or just adding there is ok? Keyboard hook was there by default.

Last edited by habit (2022-12-25 17:10:10)

Almehdin · 2022-12-25 18:01:09

You could try to move it after autodetect to see if it works better.. I don't think it will work but it might be worth a try. Just a simple thing that popped up when I read your question.

HOOKS=(base udev autodetect keyboard modconf kms keymap consolefont block filesystems fsck)

habit · 2022-12-25 19:11:33

I've tried, doesn't help

Head_on_a_Stick · 2022-12-25 19:24:31

Check the journal to see if there are any clues as to the cause of the delay.

habit · 2022-12-25 19:25:32

Head_on_a_Stick wrote:

Check the journal to see if there are any clues as to the cause of the delay.

Which commands outputs should I check? Sorry for newbie questions.

Head_on_a_Stick · 2022-12-25 19:26:58

No need to apologise. Everybody was a n00b once. Some of us still are.

https://wiki.archlinux.org/title/Systemd/Journal

habit · 2022-12-25 20:13:16

I've read journalctl output at time +- problem was gone away (about 22:50:30 sec approx).
Needed lines are red and yellow I hope, because there SO much information
Here is examples of red and yellow lines:

Dec 25 22:50:20 arch dhcpcd[433]: no valid interfaces found
Dec 25 22:50:20 arch kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Dec 25 22:50:22 arch kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Dec 25 22:50:22 arch kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Dec 25 22:50:23 arch pipewire-pulse[600]: mod.rt: Can't find xdg-portal: (null)
Dec 25 22:50:23 arch pipewire-pulse[600]: mod.rt: found session bus but no portal
Dec 25 22:50:23 arch pipewire[598]: mod.rt: Can't find xdg-portal: (null)
Dec 25 22:50:23 arch pipewire[598]: mod.rt: found session bus but no portal
Dec 25 22:50:23 arch wireplumber[599]: Failed to set scheduler settings: Operation not permitted
Dec 25 22:50:23 arch gsd-media-keys[661]: Failed to grab accelerator for keybinding settings:hibernate
Dec 25 22:50:23 arch gsd-media-keys[661]: Failed to grab accelerator for keybinding settings:playback-repeat
Dec 25 22:50:25 arch kernel: asus_wmi: Failed to get WMI notify code: AE_NOT_FOUND
Dec 25 22:50:25 arch kernel: asus_wmi: Failed to get event during flush: -5
Dec 25 22:50:25 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -61
Dec 25 22:50:25 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -61
Dec 25 22:50:25 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -61
Dec 25 22:50:25 arch kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -61
Dec 25 22:50:26 arch dhcpcd[433]: dhcpcd_prestartinterface: Operation not possible due to RF-kill <<-- this one is RED
Dec 25 22:50:27 arch systemd-udevd[360]: event23: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument <<-- another one RED
Dec 25 22:50:27 arch dhcpcd[433]: dhcpcd_prestartinterface: Operation not possible due to RF-kill <<--- RED one
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event9: Could not get device info for path /dev/input/event9: No such file or directory
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event8: GDBus.Error:System.Error.ENODEV: No such device
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event7: GDBus.Error:System.Error.ENODEV: No such device
this part i'm inserting containing normal and yellow lines:
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event9: Could not get device info for path /dev/input/event9: No such file or directory
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event8: GDBus.Error:System.Error.ENODEV: No such device
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event7: GDBus.Error:System.Error.ENODEV: No such device
Dec 25 22:50:27 arch mtp-probe[959]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9"
Dec 25 22:50:27 arch mtp-probe[959]: bus: 1, device: 7 was not an MTP device
Dec 25 22:50:27 arch kernel: input: Logitech K400 as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.2/0003:046D:C52B.0007/0003:046D:400E.0008/input/input33
Dec 25 22:50:27 arch kernel: logitech-hidpp-device 0003:046D:400E.0008: input,hidraw5: USB HID v1.11 Keyboard [Logitech K400] on usb-0000:00:14.0-9/input2:1
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event8: Could not get device info for path /dev/input/event8: No such file or directory
Dec 25 22:50:27 arch gnome-shell[528]: Could not open device /dev/input/event7: GDBus.Error:System.Error.ENODEV: No such device
Dec 25 22:50:27 arch systemd-logind[436]: Watching system buttons on /dev/input/event7 (Logitech K400)
Dec 25 22:50:27 arch systemd[1]: Manage Sound Card State (restore and store) was skipped because of an unmet condition check (ConditionPathExists=/etc/alsa/state-daemon.conf).
Dec 25 22:50:27 arch systemd[1]: Reached target Sound Card.
Dec 25 22:50:27 arch wireplumber[599]: The decibel volume range for element 'PCM' (-5006 dB - -6 dB) has negative maximum. Disabling the decibel range.
Dec 25 22:50:27 arch wireplumber[599]: The decibel volume range for element 'PCM' (-5006 dB - -6 dB) has negative maximum. Disabling the decibel range.
Dec 25 22:50:27 arch wireplumber[599]: The decibel volume range for element 'PCM' (-5006 dB - -6 dB) has negative maximum. Disabling the decibel range.
Dec 25 22:50:27 arch systemd[1]: Starting Bluetooth service...
Dec 25 22:50:27 arch bluetoothd[966]: Bluetooth daemon 5.66
Dec 25 22:50:27 arch systemd[1]: Started Bluetooth service.
Dec 25 22:50:27 arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
Dec 25 22:50:27 arch systemd[1]: Reached target Bluetooth Support.
Dec 25 22:50:27 arch bluetoothd[966]: Starting SDP server
end of part
here is red and yellow:
Dec 25 22:50:27 arch systemd[1]: Reached target Bluetooth Support.
Dec 25 22:50:27 arch bluetoothd[966]: Starting SDP server
Dec 25 22:50:27 arch bluetoothd[966]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Dec 25 22:50:27 arch bluetoothd[966]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dec 25 22:50:27 arch bluetoothd[966]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Dec 25 22:50:27 arch bluetoothd[966]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dec 25 22:50:27 arch bluetoothd[966]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Dec 25 22:50:27 arch bluetoothd[966]: src/plugin.c:plugin_init() Failed to init bap plugin
Dec 25 22:50:27 arch bluetoothd[966]: Bluetooth management interface 1.22 initialized
end
Dec 25 22:50:28 arch kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Dec 25 22:50:28 arch bluetoothd[966]: Failed to set mode: Failed (0x03)
Dec 25 22:50:33 arch gdm-password][991]: gkr-pam: unable to locate daemon control file

I thinks that's it. Full output of bigger part i'm posting here: https://pastebin.com/iccEzxLk (20-30 seconds timestamps approx.)
Gnome Logs applications shows these errors in 'Important' part:

22:50:37 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
22:50:34 systemd: Failed to start Application launched by gnome-session-binary.
22:50:33 gdm-session-wor: gkr-pam: unable to locate daemon control file
22:50:28 bluetoothd: Failed to set mode: Failed (0x03)
22:50:28 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
22:50:27 bluetoothd: src/plugin.c:plugin_init() Failed to init bap plugin
22:50:27 bluetoothd: src/plugin.c:plugin_init() Failed to init bap plugin
22:50:27 bluetoothd: src/plugin.c:plugin_init() Failed to init mcp plugin
22:50:27 bluetoothd: src/plugin.c:plugin_init() Failed to init vcp plugin
22:50:27 dhcpcd: dhcpcd_prestartinterface: Operation not possible due to RF-kill
22:50:27 systemd-udevd: event23: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
22:50:26 dhcpcd: dhcpcd_prestartinterface: Operation not possible due to RF-kill
22:50:26 dhcpcd: dhcpcd_prestartinterface: Operation not possible due to RF-kill
22:50:20 dhcpcd: no valid interfaces found

Head_on_a_Stick · 2022-12-25 20:58:05

Unless the mouse & keyboard are connecting via bluetooth nothing really stands out to me apart from the soname errors from geary.

You're supposed to

# pacman -Syu

before opening a thread so do that now. Check the news first though.

habit · 2022-12-25 21:24:12

System checks updates every GNOME start and up to date all the time. Mouth is usb wired keyboard is wireless with dongle, but disconnecting keyboard at all doesn’t fix the problem.

Last edited by habit (2022-12-26 04:52:20)

Head_on_a_Stick · 2022-12-25 21:40:55

habit wrote:

System checks updates every GNOME start

That's a really bad idea with Arch unless you've setup automatic snapshots or some other easy rollback method. Not really relevant for the problem at hand though.

Please read https://wiki.archlinux.org/title/GNOME/ … ng_updates to understand how best to deal with this.

habit wrote:

keyboard is wireless with dongle

Can you check with a wired keyboard to see if the delay still happens?

habit wrote:

Which news should I check?

That was just general advice: you should *always* check the news page on the Arch Linux website in case any manual interventions are needed for an update. Another reason not to trust GNOME's auto-updater.

habit · 2022-12-26 19:08:44

It's not GNOME's auto updater, it is archlinux update indicator with pacman && aur && flatpak update, so I'm trying to keep my system clean. But such UX problems bothers me very much.

Head_on_a_Stick · 2022-12-26 19:11:42

habit wrote:

It's not GNOME's auto updater, it is archlinux update indicator with pacman && aur && flatpak update

That's still risky. Use checkupdates(8) instead.

And now back on topic...

Arch Linux

#1 2022-12-25 15:09:29

Mouse and keyboard delay or system freeze on boot with DM.

#2 2022-12-25 16:44:31

Re: Mouse and keyboard delay or system freeze on boot with DM.

#3 2022-12-25 17:04:03

Re: Mouse and keyboard delay or system freeze on boot with DM.

#4 2022-12-25 18:01:09

Re: Mouse and keyboard delay or system freeze on boot with DM.

#5 2022-12-25 19:11:33

Re: Mouse and keyboard delay or system freeze on boot with DM.

#6 2022-12-25 19:24:31

Re: Mouse and keyboard delay or system freeze on boot with DM.

#7 2022-12-25 19:25:32

Re: Mouse and keyboard delay or system freeze on boot with DM.

#8 2022-12-25 19:26:58

Re: Mouse and keyboard delay or system freeze on boot with DM.

#9 2022-12-25 20:13:16

Re: Mouse and keyboard delay or system freeze on boot with DM.

#10 2022-12-25 20:58:05

Re: Mouse and keyboard delay or system freeze on boot with DM.

#11 2022-12-25 21:24:12

Re: Mouse and keyboard delay or system freeze on boot with DM.

#12 2022-12-25 21:40:55

Re: Mouse and keyboard delay or system freeze on boot with DM.

#13 2022-12-26 19:08:44

Re: Mouse and keyboard delay or system freeze on boot with DM.

#14 2022-12-26 19:11:42

Re: Mouse and keyboard delay or system freeze on boot with DM.

Board footer