Plymouth dumps now on every boot up since Feb 1st

English Install/Boot/Login
#1

I have been wondering why no plymouth screen appears when I boot up but only just got round to looking at this. It wold seem that after an update on 1st Feb when this was done


Feb 01 19:53:09 Tumbleweed.crowhill [RPM][15792]: install plymouth-scripts-0.9.2+git20161215.18dd755-2.1.x86_64: success
Feb 01 19:53:09 Tumbleweed.crowhill [RPM][15792]: erase plymouth-scripts-0.9.2+git20161215.18dd755-1.1.x86_64: success
Feb 01 19:53:28 Tumbleweed.crowhill [RPM][15915]: install plymouth-0.9.2+git20161215.18dd755-2.1.x86_64: success
Feb 01 19:53:28 Tumbleweed.crowhill [RPM][15915]: erase plymouth-0.9.2+git20161215.18dd755-1.1.x86_64: success
Feb 01 19:53:28 Tumbleweed.crowhill [RPM][15937]: install plymouth-plugin-script-0.9.2+git20161215.18dd755-2.1.x86_64: success
Feb 01 19:53:28 Tumbleweed.crowhill [RPM][15937]: erase plymouth-plugin-script-0.9.2+git20161215.18dd755-1.1.x86_64: success
Feb 01 19:53:28 Tumbleweed.crowhill [RPM][15938]: install plymouth-plugin-label-ft-0.9.2+git20161215.18dd755-2.1.x86_64: success
Feb 01 19:53:29 Tumbleweed.crowhill [RPM][15938]: erase plymouth-plugin-label-ft-0.9.2+git20161215.18dd755-1.1.x86_64: success
Feb 01 19:53:39 Tumbleweed.crowhill [RPM][15978]: install plymouth-dracut-0.9.2+git20161215.18dd755-2.1.x86_64: success
Feb 01 19:53:39 Tumbleweed.crowhill [RPM][15978]: erase plymouth-dracut-0.9.2+git20161215.18dd755-1.1.x86_64: success

that this happens


Feb 12 16:11:49 Tumbleweed systemd[1]: Received SIGRTMIN+20 from PID 254 (plymouthd).
Feb 12 16:11:49 Tumbleweed systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT
Feb 12 16:11:49 Tumbleweed systemd[1]: plymouth-start.service: Unit entered failed state.
Feb 12 16:11:49 Tumbleweed systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
Feb 12 16:11:50 Tumbleweed systemd-coredump[476]: Process 254 (plymouthd) of user 0 dumped core.

I though perhaps before finding this I just needed to activate it again but obviously not. I have seen the issues with the encryption and this but my system is not encrypted.

Has anyone any ideas as to why I see this please?

Stuart

#2

I’m not at all sure what is happening with Tumbleweed and Plymouth.

I originally ran into problems (no prompt for encryption). So I changed “splash=silent” to “nosplash” on the grub linux command. That got me going.

I later removed Plymouth, and that seemed better. But then another update gave me some conflicts, and reinstalling plymouth was the easiest way to solve them.

So I now have plymouth install, “nosplash” on the boot command line, and all is working. I am not seeing plymouth crashes. As I understand it, putting “nosplash” still leaves plymouth running but not showing splash.

A few days ago, I edit the grub command line during boot, changing “nosplash” back to “splash=silent”. And I got a nice splash screen but no prompt for encryption key. So I’m back with “nosplash”.

Your crashes might be dependent on the graphics card. I have Intel graphics.

In any case, I’m posting mainly to note that all is not well with plymouth. But perhaps the symptoms vary depending on the setup.

#3

My system is an AMD one with ATI graphics. I will try with splash=silent to see what happens. I normally hibernate this system so only reboot if an update requires it. The system boots fine just no plymouth screen.

Stuart

Actually I went to check and I have splash=silent.

#4

I have been getting these core dumps everywhere on nvidia and ati systems; 32bit and 64bit.

Opened a thread in the forum and have seen other threads with the problem.

I would have expected more resonance since this directly affects the tumbleweed boot process and is configured in a standard way.

Anyway after receiving no solution after several updates i decided to deactivate plymouth by adding “plymouth.enable=0 loglevel=3” and removing the “quiet” option from my kernel bootline in grub2.

Now i get a classic text-based boot sequence with a working prompt for disk encryption.

Again here i would have expected someone official using tumbleweed with disk encryption and experiencing and fixing the problem in a timely manner. I experienced the problem on at least 7 machines; nvidia/ati/32bit/64bit, you name it.

Occasionally in one of eight boots i also get a Susefirewall startup error which seems to be some kind of timing problem during boot. Persistent problems like these during boot should not happen and if they happen should be top priority.

#5

I am getting these plymouth dumps on every boot up of Tumbleweed despite the fact I have kept on updating it. Surely someone somewhere must be aware of this and doing something about it. I have seen a couple of reports for 42.2 on bugzilla but nothing seems to be happening.

Stuart

#6

Is anything happening to fix this? I am still seeing the core dump on every boot of my TW system. Surely something should be happening to resolve this.

Stuart

#7

I did not read all of the thread above, but this caught my eye.

As you are speaking to the audience of the openSUSE help forums where your fellow openSUSE users try to help other fellow openSUSE users (including you of course), this audience will not be able to fix any bugs.

We can only discuss problems and maybe decide that we also think something is a bug (I do not know if that was the general consensus above because I did not read it) and help you in suggesting what material to go with the bug, but in the end it is you (or any other one that experiences the problem) that has to file the bug report at https://bugzilla.opensuse.org/index.cgi (same user name / password as here).
And it is always a good practice to post a link to the bug report in the thread here. That will enable others to comment on it, support it and add information to it.

#8

Just checked and see I have the same problem running Tumbleweed on a Intel(R) Core™ i5-4570S CPU:

> sudo journalctl -x -b | grep plymouth
-- Subject: Unit plymouth-start.service has begun start-up
-- Unit plymouth-start.service has begun starting up.
-- Subject: Unit plymouth-start.service has finished start-up
-- Unit plymouth-start.service has finished starting up.
-- Subject: Unit systemd-ask-password-plymouth.path has finished start-up
-- Unit systemd-ask-password-plymouth.path has finished starting up.
-- Subject: Unit plymouth-switch-root.service has begun start-up
-- Unit plymouth-switch-root.service has begun starting up.
-- Subject: Unit plymouth-switch-root.service has finished start-up
-- Unit plymouth-switch-root.service has finished starting up.
-- Subject: Unit plymouth-read-write.service has begun start-up
-- Unit plymouth-read-write.service has begun starting up.
-- Subject: Unit plymouth-read-write.service has finished start-up
-- Unit plymouth-read-write.service has finished starting up.
Jun 10 09:30:40 linux-d7n9 systemd[1]: Received SIGRTMIN+20 from PID 273 (plymouthd).
Jun 10 09:30:40 linux-d7n9 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT
Jun 10 09:30:40 linux-d7n9 systemd[1]: plymouth-start.service: Unit entered failed state.
Jun 10 09:30:40 linux-d7n9 systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
Jun 10 09:30:40 linux-d7n9 systemd-coredump[1330]: Process 273 (plymouthd) of user 0 dumped core.
-- Subject: Process 273 (plymouthd) dumped core
-- Process 273 (plymouthd) crashed and dumped core.

I did not really notice, the boot is still fine, so not a big problem for me, but not a good thing.

Searching for plumouth in bugzilla shows some bug 1008489 that seems to cover this issue.

The SIGRTMIN+21 signal plymouthd sends to systemd should simply disable the verbose console boot messages – why the plymouth process should dump core as a result of that remains a mystery.
There are also the following bug reports related to the SIGRTMIN+21 signal:
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832947>
<https://bugs.freedesktop.org/show_bug.cgi?id=91590>

#9

Well i have a feeling this is going nowhere.

How can such an error in the basesystem visible everywhere in Leap 42.2 and Tumbleweed for half a year receive so little attention?

The above mentioned bug report received one answer from the assignee and he wants to close it as not being reproducible on his machine.

Then people attach a bazillion logs and dump reports and there is no further action or comment.
The bug report has been opened half a year ago.

I since have removed all traces of plymouth from my systems.

#10

Well, as I wrote in another thread today already, it’s definitely not visible everywhere.

Plymouth does work fine here (and always has) on every system I have… (intel and radeon)

And that’s likely also the reason why this is hard to track down, to reproduce, or fix.

#11

If “works” means “it displays splash screen” - it does it here as well. Still every time I boot Leap VM I get plymouthd core. As far as November 2016 (which is the oldest one recorded). So it is easy to miss the problem unless looking specifically for it, because everything appears fine.

OTOH I do not see plymouthd cores on TW VM.

#12

Now that I’ve checked (openSUSE Leap 42.2 guest), I can confirm I’m experiencing the same. (It has no impact with my activities so hadn’t made the effort to check until now.)

#13

As I wrote here https://forums.opensuse.org/showthread.php/523556-Systemd-journal-Error-logs?p=2816985#post2816985
for me it helped to change from Wicked to Network Manager.
Not sure what it has to do with Network though…

#14

My Leap VM that shows this problem is using NM, my TW VM that does not - is using wicked.

#15

Seems to me it does not get that much attention as you do not see the problem unless you look at the logs.

A fix seems to be in the pipeline, see https://build.opensuse.org/package/show/Base:System/plymouth

This fixes plymouth-start.service failure at startup for me.

My Tumbleweed installation is currently still on 0.9.2+git20161215.18dd755-2.2 so I guess it is just waiting for 0.9.2+git20170424.6fd5c6b

#16

Well, I don’t seem to get a plymouthd coredump here on my Leap 42.2 intel machine either:


wolfi@linux-lf90:~/Desktop> sudo systemctl status plymouth-start.service 
● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled)
   Active: inactive (dead) since Fre 2017-06-09 21:32:29 CEST; 1 day 14h ago
 Main PID: 226 (code=exited, status=0/SUCCESS)

Jun 09 21:31:37 linux-lf90 systemd[1]: Starting Show Plymouth Boot Screen...
Jun 09 21:31:37 linux-lf90 systemd[1]: Started Show Plymouth Boot Screen.
wolfi@linux-lf90:~/Desktop>

And btw, I am using NetworkManager.

#17

My openSUSE 42.2 install (VM guest and NetworkManager)…

# systemctl status plymouth-start.service 
● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled)
   Active: failed (Result: core-dump) since Sun 2017-06-11 19:34:43 NZST; 2h 26min ago
 Main PID: 246 (code=dumped, signal=SEGV)

Jun 10 15:38:57 linux-kgxs systemd[1]: Starting Show Plymouth Boot Screen...
Jun 10 15:38:57 linux-kgxs systemd[1]: Started Show Plymouth Boot Screen.
Jun 11 19:34:43 linux-kgxs systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV
Jun 11 19:34:43 linux-kgxs systemd[1]: plymouth-start.service: Unit entered failed state.
Jun 11 19:34:43 linux-kgxs systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
Jun 11 19:34:45 linux-kgxs systemd-coredump[1530]: Process 246 (plymouthd) of user 0 dumped core.
#18

What coredumpctl says?

#19 
wolfi@linux-lf90:~/Desktop> sudo coredumpctl root's password:
TIME                            PID   UID   GID SIG PRESENT EXE
Fre 2017-06-09 21:34:06 CEST   1824  1000   100  11   /usr/bin/oyranos-compat-gn
Fre 2017-06-09 23:57:38 CEST  14139  1001   100  11   /usr/bin/oyranos-compat-gn
Sam 2017-06-10 01:36:20 CEST  13943  1001   100  11   /opt/kf5/bin/plasmashell
Sam 2017-06-10 01:36:20 CEST  20484  1001   100   6   /usr/lib64/libexec/drkonqi
Sam 2017-06-10 01:36:20 CEST  20802  1001   100   6   /usr/lib64/libexec/drkonqi
Sam 2017-06-10 01:36:20 CEST  20483  1001   100   6   /usr/lib64/libexec/drkonqi
Sam 2017-06-10 01:37:12 CEST  14260  1001   100  11   /opt/kf5/bin/akonadi_maild
Sam 2017-06-10 01:37:16 CEST  14264  1001   100  11   /opt/kf5/bin/akonadi_notes
Sam 2017-06-10 01:37:18 CEST  20841  1001   100   6   /usr/lib64/libexec/drkonqi
Sam 2017-06-10 01:37:19 CEST  13990  1001   100   6   /opt/kf5/bin/kactivitymana
Sam 2017-06-10 01:37:23 CEST  20860  1001   100   6   /usr/lib64/libexec/kf5/kla
Sam 2017-06-10 01:37:27 CEST  13920  1001   100   6   /opt/kf5/bin/ksmserver
Sam 2017-06-10 01:37:30 CEST  14257  1001   100  11   /opt/kf5/bin/akonadi_imap_
Sam 2017-06-10 01:37:57 CEST  13905  1001   100   6   /usr/bin/kdeinit5
Sam 2017-06-10 10:13:53 CEST   1650     0     0   6   /usr/lib/YaST2/bin/y2base
Sam 2017-06-10 10:31:44 CEST   3606  1001   100  11   /usr/bin/oyranos-compat-gn
Sam 2017-06-10 14:34:44 CEST  26223  1001   100  11   /opt/kf5/bin/amarok
Sam 2017-06-10 15:01:54 CEST  26442  1001   100   6   /opt/kf5/bin/amarok
Sam 2017-06-10 19:03:24 CEST   3420  1001   100   6   /opt/kf5/bin/kactivitymana
Sam 2017-06-10 19:05:09 CEST  13691  1000   100  11   /usr/bin/oyranos-compat-gn
wolfi@linux-lf90:~/Desktop>
#20

PS, I just rebooted and plymouthd again didn’t crash:

wolfi@linux-lf90:~/Desktop> sudo systemctl status plymouth-start.service
 ● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled)
   Active: inactive (dead) since Son 2017-06-11 12:42:16 CEST; 3min 55s ago
 Main PID: 233 (code=exited, status=0/SUCCESS)


Jun 11 12:41:21 linux-lf90 systemd[1]: Starting Show Plymouth Boot Screen...
Jun 11 12:41:21 linux-lf90 systemd[1]: Started Show Plymouth Boot Screen.
wolfi@linux-lf90:~/Desktop> sudo coredumpctl 
TIME                            PID   UID   GID SIG PRESENT EXE
Son 2017-06-11 12:44:00 CEST   1853  1000   100  11   /usr/bin/oyranos-compat-gn
wolfi@linux-lf90:~/Desktop>