Boot sequence - Time until I can use manjaro (mouse/keyboard w/o response)

Hello,
since some time I have an isse with starting up manjaro. Unfortunately I can’t determine, which was the exact time.

Behavior:

  • Manjaro booting (auto-login)
  • I see the desktop and the top panel
  • I don’t have a mouse pointer
  • a windows shows up (the normal “unlock keyring”-Legitimation Window)
  • I can’t use the keyboard

Then, after appr. 30 seconds the Mouse cursor shows up and I can use the mouse and keyboard.

I don’t know which application requests the “legitimation” because it does not show an application name.
Also I have not recognized any issues wheather I give the legitimation or not.

So my questions: how to find out, what is slowing down the startup process?

What i tried:

  • plug off all USB-Devices (except mouse / keyboard, they are directly connected so the Mainboards USBs
  • look for autostart tools in “tweaks”: none
  • searching for cronjobs (crontab -e) : none
  • disable all gnome-extensions
  • totally reset gnome via tweaks
  • reinstall manjaro and after that using the same home - partition (with all configurations listed there)

All these measures had no effect. Especially the last one makes me think that its any configuration of I don’t know.
Is there any magic command which could help?

Regards,
Sönke

ok, I made another test:

I created a new user and restartet the pc with autologin this completely new user.
The was no question for any legitimation but it also took 20-25 s looking on the desktop without being able to use the mouse or keyboard.
Very annoying.

Hi @Bienenmann,

You could try inspecting the logs. The following provides an output of the current boot:

journalctl --boot --no-pager

You can also have a look at:

systemd-analye

and

systemd-analyze  blame

Provide use with the output if you wish us to take a look too.


Providing terminal output


Tip:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

pasted text

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

1 Like

Ok, I tried

systemd-analyze                                                                                                                                             INT ✘ 
Startup finished in 38.970s (firmware) + 2.304s (loader) + 5.033s (kernel) + 21.991s (userspace) = 1min 8.299s 
graphical.target reached after 21.991s in userspace.
systemd-analyze  blame

and the result was

21.257s plymouth-quit-wait.service
  389ms dev-nvme0n1p7.device
  357ms apparmor.service
  253ms lvm2-monitor.service
  243ms udisks2.service
  168ms snapd.service
  116ms user@1000.service
  109ms systemd-udev-trigger.service
   81ms systemd-journal-flush.service
   66ms boot-efi.mount
   62ms systemd-journald.service
   54ms ModemManager.service
   51ms systemd-tmpfiles-setup.service
   44ms systemd-udevd.service
   36ms systemd-random-seed.service
   25ms polkit.service
   24ms systemd-modules-load.service
   23ms systemd-timesyncd.service
   21ms dbus.service
   21ms systemd-logind.service
   20ms upower.service
   19ms plymouth-start.service
   19ms accounts-daemon.service
   18ms systemd-vconsole-setup.service
   18ms NetworkManager.service
   16ms cups.service
   15ms systemd-tmpfiles-setup-dev.service
   13ms pamac-daemon.service
   12ms systemd-fsck@dev-disk-by\x2duuid-710ca9e7\x2dccda\x2d45d6\x2dbb55\x2db0ac3f2f310e.service
   11ms systemd-fsck@dev-disk-by\x2duuid-D86D\x2d1D30.service
   11ms plymouth-read-write.service
   10ms modprobe@fuse.service
   10ms colord.service
    9ms power-profiles-daemon.service
    9ms ufw.service
    7ms gdm.service
    7ms wpa_supplicant.service
    6ms snapd.apparmor.service
    5ms dev-hugepages.mount
    5ms dev-mqueue.mount
    4ms systemd-sysctl.service
    4ms sys-kernel-debug.mount
    4ms user-runtime-dir@1000.service
    4ms sys-kernel-tracing.mount
    4ms systemd-update-utmp.service
    3ms kmod-static-nodes.service
    3ms modprobe@configfs.service
    3ms home.mount
    3ms sys-kernel-config.mount
    3ms modprobe@drm.service
    2ms systemd-remount-fs.service
    1ms systemd-user-sessions.service
    1ms alsa-restore.service
    1ms rtkit-daemon.service
    1ms tmp.mount
  650us sys-fs-fuse-connections.mount

so seems the plymouth-quit-wait.service makes problems.

So it would seem…

I don’t know how to remove/edit that, sorry. All I can do is point you here:

and

https://wiki.archlinux.org/title/Plymouth

1 Like

Ok, that was was fast from your side :wink:
Thanks a lot.

I tried do follow this but didn’t get the last step, as the links in the artikle to configure gdm / kdm are “not secure” for Firefox. So after reboot nothing worked (I think I was logged in and could see the clock on top and the shutdown menu.
I reinstalled Manjaro, which is nearly funny fast and easy using ventoy / seperated /home and a backup of installed packages list.

Now I have the starting situation but not enough time to do further tests today. I will try later.

Again, thanks for your fast help so far.

1 Like

So, plymouth has gone, finally.

The problem is still there. New systemd-analyze blame shows

721ms udisks2.service
374ms apparmor.service
284ms dev-nvme0n1p7.device
266ms lvm2-monitor.service
146ms snapd.service
119ms user@1000.service
111ms systemd-udev-trigger.service
 97ms cups.service
 69ms home-bienenmann-Musik-Musiklager.mount
 67ms ModemManager.service
 54ms systemd-modules-load.service
 50ms systemd-journald.service
 50ms systemd-journal-flush.service
 41ms systemd-udevd.service
 37ms boot-efi.mount
 33ms systemd-tmpfiles-setup-dev.service
 32ms polkit.service
 29ms systemd-logind.service
 27ms dbus.service
 24ms ufw.service
 24ms systemd-tmpfiles-setup.service
 20ms systemd-timesyncd.service
 19ms upower.service

I tried another mouse and another keyboard (cable instead of Logitech wireless). Result is the same.

Any other Idea?

:man_shrugging:

Sorry.

:sob:

hm, journalctl --boot --no-pager brought this (excerpt).

The timestamps are significant. Maybe ist has to do sth with the onboard USB-Controller.

Aug 17 11:36:35 bienenmann-pc audit: BPF prog-id=0 op=UNLOAD
Aug 17 11:36:35 bienenmann-pc audit: BPF prog-id=0 op=UNLOAD
Aug 17 11:36:35 bienenmann-pc kernel: audit: type=1334 audit(1660728995.412:140): prog-id=0 op=UNLOAD
Aug 17 11:36:36 bienenmann-pc gnome-shell[917]: updates_checker.vala:101: 0 updates found
Aug 17 11:36:48 bienenmann-pc kernel: usb 1-9: device descriptor read/64, error -110
Aug 17 11:37:04 bienenmann-pc geoclue[987]: Service not used for 60 seconds. Shutting down..
Aug 17 11:37:04 bienenmann-pc systemd[1]: geoclue.service: Deactivated successfully.
Aug 17 11:37:04 bienenmann-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 17 11:37:04 bienenmann-pc kernel: kauditd_printk_skb: 2 callbacks suppressed
Aug 17 11:37:04 bienenmann-pc kernel: audit: type=1131 audit(1660729024.102:143): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 17 11:37:04 bienenmann-pc kernel: usb 1-9: device descriptor read/64, error -110
Aug 17 11:37:04 bienenmann-pc kernel: usb usb1-port9: attempt power cycle
Aug 17 11:37:04 bienenmann-pc kernel: usb 1-9: new full-speed USB device number 11 using xhci_hcd
Aug 17 11:37:06 bienenmann-pc msm_notifier[1278]: "cinnamon-translations"
Aug 17 11:37:09 bienenmann-pc kernel: usb 1-9: Device not responding to setup address.
Aug 17 11:37:09 bienenmann-pc kernel: usb 1-9: Device not responding to setup address.
Aug 17 11:37:10 bienenmann-pc kernel: usb 1-9: device not accepting address 11, error -71
Aug 17 11:37:10 bienenmann-pc kernel: usb 1-9: new full-speed USB device number 12 using xhci_hcd
Aug 17 11:37:15 bienenmann-pc kernel: usb 1-9: Device not responding to setup address.
Aug 17 11:37:15 bienenmann-pc kernel: usb 1-9: Device not responding to setup address.
Aug 17 11:37:15 bienenmann-pc kernel: usb 1-9: device not accepting address 12, error -71
Aug 17 11:37:15 bienenmann-pc kernel: usb usb1-port9: unable to enumerate USB device
Aug 17 11:37:15 bienenmann-pc kernel: usb 1-10: new full-speed USB device number 13 using xhci_hcd
Aug 17 11:37:16 bienenmann-pc kernel: usb 1-10: New USB device found, idVendor=26ce, idProduct=01a2, bcdDevice= 0.00
Aug 17 11:37:16 bienenmann-pc kernel: usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 17 11:37:16 bienenmann-pc kernel: usb 1-10: Product: LED Controller
Aug 17 11:37:16 bienenmann-pc kernel: usb 1-10: Manufacturer: ASRock
Aug 17 11:37:16 bienenmann-pc kernel: usb 1-10: SerialNumber: A02019100900
``

Another option, see if the boot contains any errors or warnings logged:

journalctl --boot --priority=3 --no-pager

The --priority=3 argument will limit the output to only warnings and errors.

That’s all I can recommend if I don’t think of something else…

Thanks, this is a lot shorter yet enough stuff to read :frowning:

   ~  journalctl --boot --priority=3 --no-pager                                                                                                                                                                                                                                                                                                     ✔ 
Aug 17 11:36:02 bienenmann-pc gdm-autologin][849]: gkr-pam: couldn't unlock the login keyring.
Aug 17 11:36:02 bienenmann-pc systemd[854]: Failed to start Application launched by gnome-session-binary.
Aug 17 11:36:04 bienenmann-pc systemd[854]: Failed to start Application launched by gnome-session-binary.
Aug 17 11:36:17 bienenmann-pc kernel: usb 1-9: device descriptor read/64, error -110
Aug 17 11:36:29 bienenmann-pc pulseaudio[979]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Aug 17 11:36:32 bienenmann-pc kernel: usb 1-9: device descriptor read/64, error -110
Aug 17 11:36:48 bienenmann-pc kernel: usb 1-9: device descriptor read/64, error -110
Aug 17 11:37:04 bienenmann-pc kernel: usb 1-9: device descriptor read/64, error -110
Aug 17 11:37:10 bienenmann-pc kernel: usb 1-9: device not accepting address 11, error -71
Aug 17 11:37:15 bienenmann-pc kernel: usb 1-9: device not accepting address 12, error -71
Aug 17 11:37:15 bienenmann-pc kernel: usb usb1-port9: unable to enumerate USB device
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc00b8, and key code 161: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc0184, and key code 421: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc0186, and key code 423: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc018a, and key code 155: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc018e, and key code 397: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc01b6, and key code 212: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc01bc, and key code 430: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc0221, and key code 217: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc0223, and key code 172: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
Aug 17 11:37:16 bienenmann-pc systemd-udevd[541]: event11: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc00b8, and key code 161: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc0184, and key code 421: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc0186, and key code 423: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc018a, and key code 155: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc018e, and key code 397: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc01b6, and key code 212: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc01bc, and key code 430: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc0221, and key code 217: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc0223, and key code 172: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
Aug 17 13:41:59 bienenmann-pc systemd-udevd[5990]: event12: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument

I still think there’s sth wrong with maybe the usb controller on the mainboard and Manjaro.
It is a dual boot system, Windows runs fine.

FINALLY I found the solution.
After pluging off ALL SATA connections (Manjaro is on NVME drive) the Problem still was there. So I searched the BIOS and found that I had enabled onboard WAN / Bluetooth.

After switching this off the startup time increased significantly.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.