Re: Trixie - KDE Plasma startet sehr langsam

On 9/30/25 19:55, Helge Reimer wrote:
> Am Dienstag, 30. September 2025, 19:37:00 Mitteleuropäische Sommerzeit schrieb
> Siegfrid Brandstätter:
> 
>> # systemd-analyze blame
>> 36.928s e2scrub_reap.service
>> 21.673s snapd.seeded.service
>> 21.385s snapd.service
>> 16.589s blueman-mechanism.service
>> 13.089s me.proton.vpn.split_tunneling.service
>> 10.897s
> 
> Krass, wie langsam. Was ist denn das für ein Rechner?
> Mal zum Vergleich.
> 
> 7.581s nmbd.service
> 2.878s man-db.service
> 2.219s fwupd.service
> 394ms boot-efi.mount
> 391ms media-WD3TB.mount
> 383ms apt-daily-upgrade.service
> 378ms [email protected]
> 351ms media-SSD980.mount
> 348ms smartmontools.service
> 344ms home.mount
> 334ms tmp.mount
> 281ms logrotate.service
> 242ms upower.service
> 227ms dev-nvme0n1p3.device
> 181ms cpupower-gui.service
> 179ms dpkg-db-backup.service
> 165ms systemd-fsck@dev-disk-
> by\x2duuid-09b58d34\x2db93a\x2d4618\x2d98f5\x2d82563a2ff0fb.service
> 158ms [email protected]
> 156ms fwupd-refresh.service
> 151ms input-remapper-daemon.service
> 144ms colord.service
> 133ms lm-sensors.service
> 103ms systemd-udev-trigger.service
> 100ms systemd-journal-flush.service
> 100ms systemd-machine-id-commit.service
>   85ms winbind.service
>   82ms NetworkManager.service
>   76ms udisks2.service
>   72ms exim4.service
>   68ms systemd-modules-load.service
>   65ms phpsessionclean.service
>   63ms systemd-tmpfiles-clean.service
>   61ms apt-daily.service
>   58ms systemd-fsck@dev-disk-
> by\x2duuid-0b9ad2b6\x2d30f9\x2d48b3\x2d91ad\x2dec95eb08ea4f.service
>   55ms systemd-remount-fs.service
>   52ms home-helge-Bilder.mount
>   51ms ifupdown-pre.service
>   51ms power-profiles-daemon.service
>   49ms systemd-udevd.service
>   49ms virtualbox.service
>   49ms dev-disk-by\x2duuid-
> f32b26ec\x2d4a2f\x2d41ab\x2da4c5\x2d867c27c66d84.swap
>   47ms smbd.service
>   43ms cups.service
>   43ms cpupower-gui-helper.service
>   42ms modprobe@sd_mod.service
>   37ms avahi-daemon.service
>   36ms [email protected]
>   35ms systemd-journald.service
>   34ms polkit.service
>   33ms dbus.service
>   32ms switcheroo-control.service
>   29ms apt-listbugs.service
>   28ms ModemManager.service
>   28ms networking.service
>   27ms systemd-random-seed.service
>   26ms rsyslog.service
>   23ms accounts-daemon.service
>   23ms exim4-base.service
>   23ms keyboard-setup.service
>   22ms sabnzbdplus.service
>   20ms systemd-logind.service
>   19ms grub-common.service
>   19ms systemd-hostnamed.service
>   17ms cpufreqd.service
>   17ms systemd-fsck@dev-disk-by\x2duuid-563E\x2d8FA8.service
>   16ms systemd-fsck@dev-disk-
> by\x2duuid-55d680c6\x2db584\x2d4912\x2d8ba8\x2ddfe78d117a76.service
>   14ms home-helge-Filme.mount
>   12ms systemd-tmpfiles-setup.service
>   11ms systemd-boot-random-seed.service
>   10ms sysfsutils.service
>    8ms systemd-bootctl.socket
>    8ms systemd-sysctl.service
>    8ms systemd-tmpfiles-setup-dev-early.service
>    8ms e2scrub_reap.service
>    6ms wpa_supplicant.service
>    6ms rtkit-daemon.service
>    5ms dev-hugepages.mount
>    5ms dev-mqueue.mount
>    5ms sys-kernel-debug.mount
>    5ms inetd.service
>    5ms sys-kernel-tracing.mount
>    4ms systemd-udev-load-credentials.service
>    4ms systemd-tmpfiles-setup-dev.service
>    4ms kmod-static-nodes.service
>    4ms sys-kernel-config.mount
>    4ms home-helge-Steam.mount
>    4ms sys-fs-fuse-connections.mount
>    3ms console-setup.service
>    3ms systemd-user-sessions.service
>    3ms tor.service
>    3ms systemd-binfmt.service
>    2ms proc-sys-fs-binfmt_misc.mount
>    2ms mysql.service
>    1ms systemd-coredump.socket
> 477us systemd-ask-password.socket
> 423us systemd-factory-reset.socket
> 340us systemd-sysext.socket
> 330us systemd-creds.socket
>   43us uuidd.socket
>   42us cups.socket
>   18us syslog.socket
>   17us systemd-importd.socket
>   16us systemd-rfkill.socket
>   14us acpid.socket
>   12us systemd-machined.socket
>   11us dm-event.socket
>   11us systemd-journald-dev-log.socket
>    9us systemd-udevd-varlink.socket
>    9us systemd-journald.socket
>    9us avahi-daemon.socket
>    8us systemd-udevd-control.socket
>    7us pcscd.socket
>    7us dbus.socket
>    6us systemd-logind-varlink.socket
>    5us systemd-hostnamed.socket
>    4us systemd-udevd-kernel.socket
> 
> 8ms e2scrub_reap.service, bei dir fast 37s
> Mich irritieren schon die 7,5 Sekunden für nmbd.service.
> 

Hier die Werte von einem schon älteren Thinkpad SL510:

rolf@SL510-debian:~$ systemd-analyze blame
12.566s [email protected]
10.254s systemd-journal-flush.service
  8.614s e2scrub_reap.service
  7.838s dev-sda1.device
  6.899s udisks2.service
  6.577s exim4-base.service
  6.400s dpkg-db-backup.service
  5.867s accounts-daemon.service
  5.293s NetworkManager.service
  5.269s NetworkManager-wait-online.service
  4.975s cups.service
  4.578s ModemManager.service
  3.858s polkit.service
  3.747s avahi-daemon.service
  3.712s bluetooth.service
  3.634s dbus.service
  3.493s apparmor.service
  2.975s systemd-udevd.service
  2.186s wpa_supplicant.service
  2.141s exim4.service
  1.906s grub-common.service
  1.825s nginx.service
  1.815s rsyslog.service
  1.749s ssh.service
  1.739s upower.service
  1.437s plymouth-start.service
  1.283s networking.service
  1.219s systemd-tmpfiles-setup-dev-early.service
  1.014s lm-sensors.service
   946ms systemd-udev-trigger.service
   874ms lightdm.service
   850ms plymouth-quit-wait.service
   834ms alsa-restore.service