https://bugs.kde.org/show_bug.cgi?id=523054

            Bug ID: 523054
           Summary: Waiting for udev to settle before starting plasmalogin
                    adds about 5 seconds to my boot time
    Classification: Plasma
           Product: plasma-login-manager
      Version First 6.7.2
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
  Target Milestone: ---

This PR:
https://invent.kde.org/plasma/plasma-login-manager/-/merge_requests/130 seems
to have prolonged my boot up time.

Now /usr/lib/systemd/system/plasmalogin.service

has a line 

ExecStartPre=-udevadm settle --timeout=10

systemd-analyze critical-chain gives:

graphical.target @14.414s 
└─plasmalogin.service @4.135s +10.276s 
  └─plymouth-quit.service @4.098s +35ms 
    └─systemd-user-sessions.service @4.084s +8ms 
      └─remote-fs.target @4.078s 
        └─remote-fs-pre.target @4.077s 
          └─nfs-client.target @4.077s 
            └─gssproxy.service @4.026s +50ms 
              └─network.target @4.023s 
                └─wpa_supplicant.service @4.000s +22ms 
                  └─basic.target @3.004s 
                    └─dbus-broker.service @2.872s +107ms 
                      └─dbus.socket @2.858s +537us 
                        └─sysinit.target @2.848s 
                          └─systemd-binfmt.service @1.849s +998ms 
                            └─proc-sys-fs-binfmt_misc.mount @2.536s +284ms 
                              └─proc-sys-fs-binfmt_misc.automount @536ms 

When I comment it out,  systemd-analyze critical-chain gives :
graphical.target @9.871s 
└─multi-user.target @9.871s 
  └─rsyslog.service @9.816s +54ms 
    └─network-online.target @9.812s 
      └─NetworkManager-wait-online.service @4.297s +5.514s 
        └─NetworkManager.service @3.338s +957ms 
          └─network-pre.target @3.335s 
            └─firewalld.service @3.334s 
              └─basic.target @3.306s 
                └─dbus-broker.service @3.042s +206ms 
                  └─dbus.socket @3.022s +536us 
                    └─sysinit.target @3.007s 
                      └─systemd-binfmt.service @2.152s +854ms 
                        └─proc-sys-fs-binfmt_misc.mount @2.914s +83ms 
                          └─proc-sys-fs-binfmt_misc.automount @911ms

I understand this is neede on some hardware, but do we need this for the most
of us who have a hardware that does not need that?

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.3-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i9-9880H CPU @ 2.30GHz
Memory: 64 GiB of RAM (62.5 GiB usable)
Graphics Processor 1: Intel® UHD Graphics 630
Graphics Processor 2: NVIDIA GeForce GTX 1650 with Max-Q Design

I am not the only one: https://bbs.archlinux.org/viewtopic.php?id=313829

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to