Arch Linux

Raikia

Member

Registered: 2012-02-03

Posts: 5

Plymouth CPU usage

Hey all,

I have a setup with KDE5 + SDDM on a LUKS with LVM drive, and I decided to install plymouth for the graphical eye candy of the boot password screen.  However, I've found that even after I login to KDE, plymouth is taking up a consistent 30% CPU (100% of one of my CPU cores).

The plymouth wiki page is fairly outdated and I'm willing to update it, but I wanted to get some input here.  Under "Smooth Transition" ( https://wiki.archlinux.org/index.php/Pl … transition ), it mentions:

Warning: Plymouth version 0.9.2-5 has been reported to cause issues when starting LightDM. The issue is known on upstream and you should use light display managers like SLiM or SDDM for now.

However, there is no "sddm-plymouth.service" like it implies there should be.  So I copied the format of the other *-plymouth.service files and created a new one with the following content:

[Unit]
Description=SDDM Manager
Conflicts=getty@tty1.service plymouth-quit.service
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service

[Service]
ExecStart=/usr/bin/sddm
Restart=always
IgnoreSIGPIPE=no
StandardOutput=syslog

[Install]
Alias=display-manager.service

Everything starts and works 100% fine, but as I mentioned, plymouth is taking 100% cpu after I'm logged in.

For completion-sake, here is the output of "systemctl status sddm-plymouth.service":

● sddm-plymouth.service - SDDM Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm-plymouth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2015-12-27 11:45:54 CST; 21min ago
Main PID: 619 (sddm)
   CGroup: /system.slice/sddm-plymouth.service
           ├─619 /usr/bin/sddm
           └─640 /usr/lib/xorg-server/Xorg -nolisten tcp -auth /var/run/sddm/{71b0654d-a43d-45fe-ab4a-3259901bad65} -background none -noreset -displayfd 17 vt7

Dec 27 11:45:58 darkburn sddm-helper[5362]: [PAM] Preparing to converse...
Dec 27 11:45:58 darkburn sddm-helper[5362]: [PAM] Conversation with 1 messages
Dec 27 11:45:58 darkburn sddm-helper[5362]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Dec 27 11:45:58 darkburn sddm-helper[5362]: [PAM] returning.
Dec 27 11:45:58 darkburn sddm[619]: Authenticated successfully
Dec 27 11:45:58 darkburn sddm-helper[5362]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Dec 27 11:45:58 darkburn sddm-helper[5362]: pam_unix(sddm:session): session opened for user raikia by (uid=0)
Dec 27 11:45:58 darkburn sddm[619]: Auth: sddm-helper exited successfully
Dec 27 11:45:58 darkburn sddm[619]: Greeter stopped.
Dec 27 11:45:58 darkburn sddm[619]: Session started

I can just write a script that auto-runs on KDE start that kills plymouth, but that is dirty and I want to fix the problem instead of band-aiding it.

Any ideas?

NeS0

Member

Registered: 2016-10-29

Posts: 1

Re: Plymouth CPU usage

You should check if plymouth-quit.service is enabled by running

# systemctl status plymouth-quit