Description of problem: plymouth takes over gnome-shell lock screen after resume from ram. $ systemctl status plymouth-start plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; disabled) Active: active (running) since So 2014-01-12 14:23:11 CET; 1 weeks 1 days ago Main PID: 10183 (plymouthd) CGroup: /system.slice/plymouth-start.service └─10183 @usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session Jan 16 20:13:43 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. Jan 16 20:14:02 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. Jan 16 20:14:17 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. Version-Release number of selected component (if applicable): Name : plymouth Architektur : x86_64 Version : 0.8.9 Ausgabe : 3.2013.08.14.fc20 How reproducible: Always. Steps to Reproduce: 1. Suspend gnome-shell to ram. 2. Resume from ram 3. See Fedora logo instead of gnome-lock screen. Actual results: Expected results: Additional info:
I also have this problem here are the versions of the plymouth packages: plymouth-plugin-label-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-theme-charge-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-core-libs-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-scripts-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-system-theme-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-plugin-two-step-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-0.8.9-3.2013.08.14.fc20.x86_64 plymouth-graphics-libs-0.8.9-3.2013.08.14.fc20.x86_64 There isn't much that stands out to me in journalctl -r
Hi, I think this problem is related to systemd and the upgrade of libc After a fresh reboot this problem doesn't show up. It begins to show up, after upgrading the system via yum and don't reboot immediately, but continue to use the system as normal. this is the logs I found: $ systemctl status plymouth-start plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; disabled) Active: active (running) since Di 2014-02-04 20:41:15 CET; 2 days ago Main PID: 5215 (plymouthd) CGroup: /system.slice/plymouth-start.service └─5215 @usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach... Started at 04.02.2014 20:41:15. look at the rpm that got installed at this time: $ rpm -qa --last curl-7.32.0-4.fc20.x86_64 Di 04 Feb 2014 20:41:17 CET pango-1.36.1-2.fc20.x86_64 Di 04 Feb 2014 20:41:16 CET libcurl-7.32.0-4.fc20.x86_64 Di 04 Feb 2014 20:41:13 CET glibc-2.18-12.fc20.x86_64 Di 04 Feb 2014 20:41:06 CET glibc-common-2.18-12.fc20.x86_64 Di 04 Feb 2014 20:40:57 CET So this is maybe related to the upgrade of the libc. $ journalctl --since="2014-02-04 20:41:00" --until="2014-02-04 20:42:00" -- Logs begin at Sa 2013-06-29 22:06:32 CEST, end at Do 2014-02-06 20:59:16 CET. -- Feb 04 20:41:03 localhost.localdomain yum[4735]: Updated: glibc-common-2.18-12.fc20.x86_64 Feb 04 20:41:09 localhost.localdomain systemd[1]: Reexecuting. Feb 04 20:41:09 localhost.localdomain systemd[1]: systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) Feb 04 20:41:11 localhost.localdomain systemd[1]: Mounted POSIX Message Queue File System. [...] Feb 04 20:41:12 localhost.localdomain systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Feb 04 20:41:12 localhost.localdomain systemd[1]: Starting Show Plymouth Boot Screen... Feb 04 20:41:12 localhost.localdomain systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... [...] Feb 04 20:41:15 localhost.localdomain yum[4735]: Updated: libcurl-7.32.0-4.fc20.x86_64 Feb 04 20:41:16 localhost.localdomain restorecond[620]: wd=3 mask=256 cookie=0 len=16 Feb 04 20:41:15 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. So the upgrade of glibc triggers a reexecution of systemd, which restarts the plymouth-start.service. I'm not sure if this is correct... Help appreciated!
*** This bug has been marked as a duplicate of bug 1043212 ***