Comment 11 for bug 1478322

Hi David,

The SDDM version that I am using is from git master and we are building it on openSUSE Build Service. I am part of the openSUSE KDE Community team and we are currently testing SDDM to see if we could make the same switch as Fedora from KDM to SDDM. I am using it in connection with a Frameworks/Plasma-next desktop.

SDDM on openSUSE is started through the generic display-manager service. There are indications that we should switch to using separate services for each display-manager, but this has not yet done, so you might see display-manager in the journal logs.

Running systemd-analyze blame delivers (top x lines) the following output:
    1min 30.078s display-manager.service
           560ms ModemManager.service
           536ms systemd-tmpfiles-setup.service
           500ms systemd-logind.service
           499ms firewalld.service
           447ms postfix.service
           429ms plymouth-read-write.service
           214ms mnt-windows.mount
           159ms NetworkManager.service
            67ms lvm2-activation-net.service
            58ms systemd-fsck@dev-disk-by\x2duuid-a15e9da3\x2d0009\x2d4847\x2d978d\x2d34b3de059089.service
            42ms alsa-restore.service
            40ms avahi-daemon.service

So I am not sure if the 1min 30secs is really the time required by SDDM or that it just indicates that a total boot time of 1 min is reached and that 30 secs is used for the display-manager.

I have attached two journals (one with the maldives theme active and the other with the breeze theme). These are the full startup journals of the current session. I didn't filter them to prevent loosing information.