Ubuntu
plasma-workspace package

SDDM-init is slow with SDDM theme Breeze

Bug #1478322 reported by Blaze
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kde-workspace
Fix Released
Medium
plasma-workspace (Ubuntu)
Confirmed
High
Unassigned

Bug Description

SDDM starts really slow when Breeze theme is enabled. It takes about 17 seconds to see the login screen after X server init.

There are also huge amount of deprecated messages and QThread errors in sddm.log (see the attachment).

$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04

$ apt-cache policy plasma-workspace
plasma-workspace:
  Installed: 4:5.2.2-0ubuntu3
  Candidate: 4:5.2.2-0ubuntu3
  Version table:
 *** 4:5.2.2-0ubuntu3 0
        500 http://by.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
In , Tittiatcoke (tittiatcoke) wrote :

Due to the very nice integration with the rest of the desktop, I am using the Breeze theme for SDDM (created by David Edmundson). It looks way better than the default theme of SDDM, but it has one very big disadvantage. When the Breeze theme is active, it takes about 1,5 minute for SDDM to show its login screen. (Measured with systemd-analyze blame). Using the default theme for SDDM (Maui), then it only takes a fraction of a second and systemd-analyze blame doesn't even show a line for it.

The only difference that I notice is that is feels that it takes longer for plasma to startup when using the Maui theme, then with the Breeze theme. However these few seconds still doesn't justify the 1,5 minutes startup for SDDM.

Reproducible: Always

Revision history for this message
In , U26 (u26) wrote :

wow. That's pretty extreme

A delay that big must be a DBus timeout (or rather 3 sequential DBus timeouts).

We end up querying solid for battery status which does go via an activated kded; so potentially that's where we block.

Can you:
 - confirm what version you are using.
 - tell me where you get your RPMs from
 - check the log files from SDDM (journalctl -u sddm)

Revision history for this message
In , Tittiatcoke (tittiatcoke) wrote :

Created attachment 89915
journalctl -b output with Breeze theme active for SDDM

Revision history for this message
In , Tittiatcoke (tittiatcoke) wrote :

Created attachment 89916
journalctl -b output with Maldives theme active for SDDM

Revision history for this message
In , Tittiatcoke (tittiatcoke) wrote :

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.

Revision history for this message
In , 8p-k26-gj (8p-k26-gj) wrote :

I reverted the PowerDevil patch. Please try again with recent PowerDevil. Thanks!

Revision history for this message
In , Tittiatcoke (tittiatcoke) wrote :

Hi Kai,

I hope your didn't revert your patch because of this bug report. I am running the latest version from git, but still the same issue. So the revert didn't bring any relief in the startup time of SDDM

Revision history for this message
Blaze (blaze) wrote :
Revision history for this message
Blaze (blaze) wrote :

Also in Wily. A bit faster but still slow.

Flames_in_Paradise (ellisistfroh-deactivatedaccount)
tags: added: vivid
tags: added: wily
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plasma-workspace (Ubuntu):
status: New → Confirmed
Alberto Salvia Novella (es20490446e)
Changed in plasma-workspace (Ubuntu):
importance: Undecided → High
Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

What is slow? Let's try to be objective in bug-reports.

Pls. provide log of

journalctl -u sddm

and attach it to the report.

I would either assume, that this is not reported against the right package, when SDDM has finished the DE (Plasma) continues to provide a GUI and such.

Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

There are other commands allowing you to analyse (no relation to sddm-theme)

systemd-analyze blame

systemd-analyze critical-chain

see: man systemd

Last not least SDDM+1 will contain sddm-theme-maui as fallback - so you can test if it's "faster" with that.

A good hint is to disable Desktop-restauration, don't know why this is enabled by default (?). Always start with an empty desktop-session – speedy.

Revision history for this message
Blaze (blaze) wrote :

Sddm log is already attached. Maui theme is ~4 times faster. I don't do login to desktop session.

Revision history for this message
In , Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

@ Raymond

Starting with Plasma 5.5.4 you can select not to have a start screen (with progress-bar) at all

System-Settings -> Desktop-Appearance -> Start-Screen (select)

Does this speed up your boot?

<OT >There's nothing yet from kde-look.org <OT>

Bug Watch Updater (bug-watch-updater)
Changed in kde-workspace:
importance: Unknown → Medium
status: Unknown → New
Flames_in_Paradise (ellisistfroh-deactivatedaccount)
summary: - SDDM init is slow with SDDM theme Breeze
+ Plasma-init is slow with SDDM theme Breeze
Revision history for this message
Blaze (blaze) wrote :

Why Plasma? I don't even use Plasma. I'm using Openbox.

summary: - Plasma-init is slow with SDDM theme Breeze
+ SDDM-init is slow with SDDM theme Breeze
Revision history for this message
Blaze (blaze) wrote :

The situation is better for Xenial. Probably fixed.

Changed in plasma-workspace (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Blaze (blaze) wrote :

The problem still exist on Yakkety.

Changed in plasma-workspace (Ubuntu):
status: Fix Committed → Confirmed
Revision history for this message
In , Blaze (blaze) wrote :

Can confirm this for Plasma 5.7.x (K)Ubuntu 16.10 YY.

Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

@ Blaze: yr. complaint doesn't cover a standard-installation. Doesn't help though on a regular bug-report, w/o mentioning such special-cases... This is were LP-bug-reporting is weak. Even LVM could cause straints. So anything as such needs to be added, preferably. That makes the difference on reporting bugs. "me too" is just not enough...

Anyway since SDDM is a thirdparty-SW iT's appreciated to report such there.

SDDM Version 0.14 is out now since 1 months time (perfect changelog in their wiki !) & it will probably not make it into Yakkety 16.10? With the changelog listing, it should be easy for Dev's to cherrypick and probably backport important bugfixes.

Maybe you wish to build it yourself, for testing if this resolves your issues with Openbox? [1]

[1] http://www.linuxfromscratch.org/blfs/view/svn/x/sddm.html

Haven't tested this yet, since I mainly use a rolling-release. Also notice, that Plasma 5.8 will have a huge change on their SDDM-theme (unified look).

Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

@ Blaze: Excuses, forgot the other link on the release notes SDDM 0.14 [2]

[2] https://github.com/sddm/sddm/wiki/0.14.0-Release-Announcement

Any change listed there has a link to the GIT-commit.

SDDM 0.14 should be merged once it's done in Debian, to avoid Ubuntu's lagging behind.

Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

@ Blaze or anybody else effected:

Pls. feel free to support bug #1627340 -
[Request Upgrade software-version] SDDM 0.14.0]

Revision history for this message
In , Blaze (blaze) wrote :

I think that problem here is more global than just sddm plugin. Slow init can reproduced for a quite big number of Qt5 apps. Maybe linking against libicu causes this issue or opensource graphics drivers. Not sure. Needs further investigation.

Revision history for this message
In , Tittiatcoke (tittiatcoke) wrote :

Actually I haven't seen this for quite some time. Also with the changes that Plasma 5.8 will bring to the SDDM theme, the issue no longer occurs with me.

Revision history for this message
In , Blaze (blaze) wrote :

Maybe it was fixed with Qt5.7. I have Qt5.6.1.

Revision history for this message
In , Rik Mills (rikmills) wrote :

I also cannot replicate this at all:

Plasma 5.7.2, and later 5.7.5
Qt 5.6.1
Ubuntu 16.10 (Yakkety)

Revision history for this message
In , Filipfila-kde (filipfila-kde) wrote :

Is this still relevant?

Revision history for this message
In , Nate-b (nate-b) wrote :

Since there have been changes relevant to this bug since it was filed, and folks can no longer reproduce it, let's close it until we get new reports. Thanks everyone!

Revision history for this message
In , Nate-b (nate-b) wrote :

*** Bug 365710 has been marked as a duplicate of this bug. ***

Bug Watch Updater (bug-watch-updater)
Changed in kde-workspace:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.