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?
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.
Ok, that was was fast from your side
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.
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
``
Thanks, this is a lot shorter yet enough stuff to read
~ 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.