Hi forumers,
any suggestion of how to resolve sddm slow start after reboot on my Tumbleweed KDE system? The system boots to graphics and shows black screen with just a mouse cursor on it for 15-30 secs before sddm login screen appears. Happens not always but 9 out of 10 reboots run as described.
Can you share for a slow start the output of:
$ sudo systemd-analyze blame
$ sudo systemd-analyze critical-chain
You can do likely a first analysis yourself if you dump that also do that 1 out 10 runs that is not slow and compare them.
Sure. Here it is:
28.806s upower.service
14.199s postfix.service
9.463s backup-rpmdb.service
4.906s yast-timesync.service
2.264s logrotate.service
1.790s dracut-initqueue.service
1.433s plymouth-switch-root.service
1.086s mandb.service
895ms dracut-pre-udev.service
809ms plymouth-read-write.service
642ms display-manager.service
421ms vboxdrv.service
378ms firewalld.service
373ms initrd-switch-root.service
262ms systemd-backlight@backlight:intel_backlight.service
136ms systemd-journal-flush.service
133ms plymouth-quit-wait.service
128ms systemd-udevd.service
106ms bolt.service
94ms initrd-parse-etc.service
84ms user@1000.service
70ms systemd-logind.service
62ms cups.service
61ms systemd-udev-trigger.service
56ms polkit.service
48ms apparmor.service
44ms systemd-vconsole-setup.service
42ms ModemManager.service
40ms mcelog.service
39ms dev-disk-by\x2duuid-5c57b34c\x2daf7a\x2d4459\x2da7a9\x2dbdcdc66ae8b4.swap
38ms smartd.service
37ms systemd-rfkill.service
32ms avahi-daemon.service
29ms backup-sysconfig.service
27ms udisks2.service
27ms kbdsettings.service
25ms modprobe@fuse.service
25ms dracut-cmdline.service
24ms NetworkManager.service
24ms boot-efi.mount
23ms systemd-journald.service
20ms systemd-fsck-root.service
19ms systemd-random-seed.service
18ms check-battery.service
17ms issue-generator.service
16ms systemd-tmpfiles-clean.service
16ms systemd-sysctl.service
16ms auditd.service
15ms sysroot.mount
15ms systemd-tmpfiles-setup.service
14ms plymouth-start.service
14ms systemd-fsck@dev-disk-by\x2duuid-CB9C\x2dA28E.service
14ms nscd.service
13ms bluetooth.service
13ms modprobe@configfs.service
10ms initrd-cleanup.service
8ms modprobe@drm.service
8ms var.mount
8ms \x2esnapshots.mount
7ms vboxautostart-service.service
7ms boot-grub2-i386\x2dpc.mount
7ms user-runtime-dir@1000.service
7ms boot-grub2-x86_64\x2defi.mount
7ms dev-hugepages.mount
7ms systemd-tmpfiles-setup-dev.service
7ms home.mount
6ms dev-mqueue.mount
6ms systemd-modules-load.service
6ms opt.mount
6ms sys-kernel-debug.mount
6ms root.mount
6ms sys-kernel-tracing.mount
6ms rtkit-daemon.service
6ms systemd-remount-fs.service
6ms srv.mount
6ms systemd-update-utmp-runlevel.service
5ms usr-local.mount
5ms kmod-static-nodes.service
5ms wpa_supplicant.service
4ms systemd-update-utmp.service
4ms systemd-user-sessions.service
3ms initrd-udevadm-cleanup-db.service
2ms sys-fs-fuse-connections.mount
2ms dracut-shutdown.service
2ms tmp.mount
1ms sound-extra.service
1ms sys-kernel-config.mount
1ms alsa-restore.service
graphical.target @15.788s
└─multi-user.target @15.788s
└─cron.service @15.788s
└─network.target @1.585s
└─NetworkManager.service @1.560s +24ms
└─network-pre.target @1.560s
└─wpa_supplicant.service @2.037s +5ms
└─dbus.service @1.120s
└─basic.target @1.119s
└─sockets.target @1.119s
└─pcscd.socket @1.119s
└─sysinit.target @1.117s
└─plymouth-read-write.service @308ms +809ms
└─local-fs.target @306ms
└─boot-efi.mount @281ms +24ms
└─systemd-fsck@dev-disk-by\x2duuid-CB9C\x2dA28E.service @267ms +14ms
└─local-fs-pre.target @262ms
└─systemd-tmpfiles-setup-dev.service @255ms +7ms
└─kmod-static-nodes.service @244ms +5ms
└─systemd-journald.socket
└─system.slice
└─-.slice
Was the output of “sudo systemd-analyze critical-chain” not interesting?
The first two links on a search for “upower.service” give me:
Please try some of the suggestions there and if that does not work out, please post the interesting parts of what you tried here
Seems it was my keyboard/mouse connected via USB KVM switch - system was whining about some errors with USB. After I did connect them directly to laptop’s usb port it stopped complaining and boots much faster and there is no upower in boot sequence in "systemd-analyze blame
" output.