Plymouth dumps now on every boot up since Feb 1st

For me, running Tumbleweed with Wicked I get:

> sudo coredumpctl | tail
Fri 2017-06-02 20:34:48 CEST    295     0     0   6 missing  /usr/sbin/plymouthd
Fri 2017-06-02 20:50:26 CEST   7962  1000   100  11 none     /usr/bin/ksysguard
Sat 2017-06-03 09:03:02 CEST    268     0     0   6 missing  /usr/sbin/plymouthd
Sat 2017-06-03 14:11:48 CEST    286     0     0   6 missing  /usr/sbin/plymouthd
Mon 2017-06-05 21:35:56 CEST    295     0     0   6 missing  /usr/sbin/plymouthd
Wed 2017-06-07 20:01:10 CEST    290     0     0   6 missing  /usr/sbin/plymouthd
Fri 2017-06-09 20:24:16 CEST    271     0     0   6 present  /usr/sbin/plymouthd
Sat 2017-06-10 09:30:40 CEST    273     0     0   6 present  /usr/sbin/plymouthd
Sat 2017-06-10 18:33:56 CEST    276     0     0   6 present  /usr/sbin/plymouthd
Sun 2017-06-11 09:14:41 CEST    300     0     0   6 present  /usr/sbin/plymouthd

would just disabling plymouth from grub cmd not resolve the issue?

Yes, disabling plymouth from grub cmd would work-around the issue and as plymouth is more-or-less just eye-candy it would not be a problem either.
The things is that it is by default installed so better have it working.

I followed this thread since it seems I have the same problem with Tumbleweed and plymouth. In the end it proceeds to a graphical log-in screen after sitting a while in the login for command line.
I too have the plymouth-0.9.2+git20161215.18dd755-2.2.i586 package. In the link above the update to version 0.9.2+git20170424.6fd5c6b was via a tar.gz file. Although I have the odd tar.gz files installed I prefer the rpm version then it is in the database for updates.
Unlike wolfi323 I get with

systemctl status plymouth-start.service
● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset
   Active: failed (Result: core-dump) since Mon 2017-06-12 12:54:56 NZST; 8min ago
 Main PID: 241 (code=dumped, signal=ABRT)

Cheers
Uli

Well all I can say is that my Tumbleweed system running with Network Manager core dumps plymouth on every boot up of the system. This is running on the metal NOT under any VM. My Leap 42.2 laptop does not have the issue though. As soon as that update is available for TW I’ll see what happens.

Stuart

Have installed the Leap 42.2 Plymouth patch a few minutes ago – Plymouth version 0.9.2-5.1 – rebooted a couple of times – Plymouth no longer dumps core – need to write a comment in the openSUSE bug report I raised some time ago (last autumn if correctly recall . . . )

# 2017-06-12 15:33:30 plymouth-0.9.2-5.1.x86_64.rpm installed ok

I am not convinced that it is fixed though (rather than timing changed hiding this issue). This bug is not mentioned in changelog and none of bugs mentioned in changelog can be viewed by mere mortals so we have no way to actually compare symptoms.

Correct!!!
It still doesn’t display the graphics correctly but, it no longer dumps core . . .

I’ve seen core dumps (using Tumbleweed) many times since the early part of the year, and therefore have had plymouth disabled.

So I thought it time to give it another try. (Tumbleweed 20170612)

Still core dumps on this system:

● 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 Fri 2017-06-16 12:30:07 BST; 3min 4s ago
  Process: 535 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=2)
  Process: 433 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
 Main PID: 487 (code=dumped, signal=SEGV)

Jun 16 12:30:05 Orion-Tumble systemd[1]: Starting Show Plymouth Boot Screen...
Jun 16 12:30:07 Orion-Tumble plymouth[535]: error: unexpectedly disconnected from boot status daemon
Jun 16 12:30:07 Orion-Tumble systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV
Jun 16 12:30:07 Orion-Tumble systemd[1]: Failed to start Show Plymouth Boot Screen.
Jun 16 12:30:07 Orion-Tumble systemd[1]: plymouth-start.service: Unit entered failed state.
Jun 16 12:30:07 Orion-Tumble systemd[1]: plymouth-start.service: Failed with result 'core-dump'.

Only difference is I don’t recall seeing this line before:

Jun 16 12:30:07 Orion-Tumble plymouth[535]: error: unexpectedly disconnected from boot status daemon

I’ve just update TW today and on rebooting plymouth dumped still. It is version 0.9.2+git20170424.6fd5c6b-1.1 which version is supposed to address this?

Stuart

I can confirm, also Plymouth Version 0.9.2+git20170424.6fd5c6b-1.1 on TW but still the same problem:

> 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: failed (Result: core-dump) since Fri 2017-06-23 19:41:00 CEST; 19min ago
 Main PID: 279 (code=dumped, signal=ABRT)

Jun 23 19:40:54 linux-d7n9 systemd[1]: Starting Show Plymouth Boot Screen...
Jun 23 19:40:54 linux-d7n9 systemd[1]: Started Show Plymouth Boot Screen.
Jun 23 19:41:00 linux-d7n9 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT
Jun 23 19:41:00 linux-d7n9 systemd[1]: plymouth-start.service: Unit entered failed state.
Jun 23 19:41:00 linux-d7n9 systemd[1]: plymouth-start.service: Failed with result 'core-dump'.

I was hopeful that this new version would fix things as a comment on https://build.opensuse.org/package/show/Base:System/plymouth was saying the new version was fixing a problem; I can not find that comment anymore…

Feel free to update Bug 1008489

No core dump here (Tumbleweed + Network Manager), never had one (or so coredumpctl says).
Besides the fact that I’ve not had a splash screen since ages, Plymouth is working “correctly” here.

I’m on AMD graphics:

cris@PolariSuse ~]**$** inxi -G
**Graphics: ****Card:** Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
**Display Server:** X.Org 1.19.3 **drivers:** ati,radeon (unloaded: modesetting,fbdev,vesa)
**Resolution:** 1920x1080@60.00hz
**GLX Renderer:** Gallium 0.4 on AMD CAICOS (DRM 2.49.0 / 4.11.6-1-default, LLVM 4.0.0)
**GLX Version:** 3.0 Mesa 17.1.3

Cris

Well I have ATI gfx card and AMD processor and I get them on every boot.


coredumpctl
TIME                            PID   UID   GID SIG COREFILE  EXE
Sun 2017-06-11 10:42:10 BST     259     0     0   6 missing   /usr/sbin/plymouthd
Mon 2017-06-12 07:41:05 BST     289     0     0   6 missing   /usr/sbin/plymouthd
Mon 2017-06-12 13:02:01 BST     286     0     0   6 missing   /usr/sbin/plymouthd
Mon 2017-06-12 17:27:36 BST     270     0     0   6 missing   /usr/sbin/plymouthd
Wed 2017-06-14 07:44:04 BST     262     0     0   6 missing   /usr/sbin/plymouthd
Fri 2017-06-16 07:43:26 BST     286     0     0   6 missing   /usr/sbin/plymouthd
Fri 2017-06-16 09:32:03 BST     269     0     0   6 missing   /usr/sbin/plymouthd
Tue 2017-06-20 09:26:42 BST     269     0     0   6 missing   /usr/sbin/plymouthd
Fri 2017-06-23 09:29:07 BST     246     0     0   6 error     /usr/sbin/plymouthd
Sun 2017-06-25 08:10:38 BST     257     0     0   6 error     /usr/sbin/plymouthd
Sun 2017-06-25 10:38:15 BST     253     0     0   6 error     /usr/sbin/plymouthd
Sun 2017-06-25 12:12:45 BST     246     0     0   6 error     /usr/sbin/plymouthd

Stuart

I’ve been wondering when someone might fix this for some time now. I know it is relatively minor in that the system comes up OK but it does not look good to see all those text messages scrolling past on the monitor when it should be displaying the logo. What do I need to do to get this progressed further? I gather that there are already bugs open for this.

Stuart

Decided to do a bit more and looked up some debug techniques for plymouth. So added plymouth:debug manually to a boot which showed the following in boot.log


Jul 15 09:53:44 Tumbleweed kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.11.8-1-default root=UUID=17e8a259-e43e-46c3-89ba-7c97536998ee resume=/dev/sdb3 splash=silent showopts plymouth:debug
Jul 15 09:53:44 Tumbleweed kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.11.8-1-default root=UUID=17e8a259-e43e-46c3-89ba-7c97536998ee resume=/dev/sdb3 splash=silent showopts plymouth:debug
Jul 15 09:53:44 Tumbleweed dracut-cmdline[164]: Using kernel command line parameters: resume=UUID=33bc4e7f-d872-4d01-8179-2effa922e8ce root=UUID=17e8a259-e43e-46c3-89ba-7c97536998ee rootfstype=btrfs rootflags=rw,relatime,space_cache,subvolid=258,subvol=/.snapshots/1/snapshot,subvol=.snapshots/1/snapshot BOOT_IMAGE=/boot/vmlinuz-4.11.8-1-default root=UUID=17e8a259-e43e-46c3-89ba-7c97536998ee resume=/dev/sdb3 splash=silent showopts plymouth:debug
Jul 15 09:53:44 Tumbleweed plymouthd[242]: [main.c:1948]                               check_verbosity:redirecting debug output to /dev/tty7
Jul 15 09:53:44 Tumbleweed plymouth[294]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jul 15 09:53:44 Tumbleweed plymouth[294]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jul 15 09:53:44 Tumbleweed plymouth[294]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jul 15 09:53:44 Tumbleweed plymouth[294]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jul 15 09:53:44 Tumbleweed plymouth[294]: ./ply-boot-client.c:795]        ply_boot_client_detach_from_event_loop:detaching from event loop
Jul 15 09:53:50 Tumbleweed systemd[1]: Received SIGRTMIN+20 from PID 243 (plymouthd).
Jul 15 09:53:50 Tumbleweed plymouthd[242]: plymouthd: ply-event-loop.c:726: ply_event_loop_watch_fd: Assertion `fd >= 0' failed.
Jul 15 09:53:56 Tumbleweed plymouth[986]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jul 15 09:53:56 Tumbleweed plymouth[986]: [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
Jul 15 09:54:20 Tumbleweed plymouth[986]: [ply-event-loop.c:1060]   ply_event_loop_handle_disconnect_for_source:calling disconnected_handler 0x5582a70986f0 for fd 6
Jul 15 09:54:20 Tumbleweed plymouth[986]: [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
Jul 15 09:54:20 Tumbleweed plymouth[986]: [ply-event-loop.c:768]               ply_event_loop_stop_watching_fd:source for fd 6 is already disconnected
Jul 15 09:54:20 Tumbleweed plymouth[986]: error: unexpectedly disconnected from boot status daemon
Jul 15 09:54:20 Tumbleweed plymouth[986]: ./plymouth.c:414]                                 on_disconnect:disconnect
Jul 15 09:54:20 Tumbleweed plymouth[986]: [ply-event-loop.c:1064]   ply_event_loop_handle_disconnect_for_source:done calling disconnected_handler 0x5582a70986f0 for fd 6
Jul 15 09:54:20 Tumbleweed plymouth[986]: [ply-event-loop.c:1144]   ply_event_loop_free_destinations_for_source:freeing destination (0, (nil), 0x5582a70986f0) of fd 6
Jul 15 09:54:20 Tumbleweed plymouth[986]: [ply-event-loop.c:1144]   ply_event_loop_free_destinations_for_source:freeing destination (1, 0x5582a7097f00, (nil)) of fd 6
Jul 15 09:54:20 Tumbleweed plymouth[986]: ./ply-boot-client.c:795]        ply_boot_client_detach_from_event_loop:detaching from event loop
Jul 15 09:54:20 Tumbleweed systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT
Jul 15 09:54:20 Tumbleweed systemd[1]: plymouth-start.service: Unit entered failed state.
Jul 15 09:54:20 Tumbleweed systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
Jul 15 09:54:21 Tumbleweed systemd-coredump[1050]: Process 243 (plymouthd) of user 0 dumped core.
Jul 15 09:54:34 Tumbleweed.crowhill display-manager[1326]: ./ply-boot-client.c:183]                       ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused
Jul 15 09:54:34 Tumbleweed.crowhill display-manager[1326]: ./plymouth.c:1121]                                          main:daemon not running

and then tried to run post boot in a console


plymouthd --debug --tty=`tty` --no-daemon
[main.c:2038]                        initialize_environment:initializing minimal work environment
[main.c:1858]                       get_kernel_command_line:opening /proc/cmdline
[main.c:1866]                       get_kernel_command_line:reading kernel command line
[main.c:1886]                       get_kernel_command_line:Kernel command line is: 'BOOT_IMAGE=/boot/vmlinuz-4.11.8-1-default root=UUID=17e8a259-e43e-46c3-89ba-7c97536998ee resume=/dev/sdb3 splash=silent showopts plymouth.debug
'
[main.c:1900]                               check_verbosity:checking if tracing should be enabled
[main.c:1911]                               check_verbosity:tracing should be enabled!
[main.c:1948]                               check_verbosity:redirecting debug output to /dev/pts/2
[main.c:1984]                                 check_logging:checking if console messages should be redirected and logged
[main.c:1993]                                 check_logging:logging will be enabled!
[main.c:2065]                        initialize_environment:source built on 2017-06-14 06:17:40.000000000 +0000
[main.c:2075]                        initialize_environment:Making sure /run/plymouth exists
[ply-utils.c:714]                          ply_create_directory:directory '/run/plymouth' already exists
[main.c:2079]                        initialize_environment:initialized minimal work environment
[main.c:747]                       get_cache_file_for_mode:returning cache file '/var/lib/plymouth//boot-duration'
[main.c:301]                                 load_settings:Trying to load /etc/plymouth//plymouthd.conf
[ply-key-file.c:171]                       ply_key_file_load_group:trying to load group Daemon
[ply-key-file.c:259]                      ply_key_file_load_groups:key file has no more groups
[main.c:315]                                 load_settings:Checking if /run/plymouth/themes/openSUSE/openSUSE.plymouth exists
[main.c:318]                                 load_settings:/run/plymouth/themes/openSUSE/openSUSE.plymouth not found, fallbacking to /usr/share/plymouth/themes/
[ply-key-file.c:352]                        ply_key_file_get_value:key file does not have entry for key 'ShowDelay'
[ply-key-file.c:352]                        ply_key_file_get_value:key file does not have entry for key 'DeviceTimeout'
[ply-key-file.c:352]                        ply_key_file_get_value:key file does not have entry for key 'DeviceScale'
[main.c:481]                    find_system_default_splash:System configured theme file is '/usr/share/plymouth/themes/openSUSE/openSUSE.plymouth'
[main.c:301]                                 load_settings:Trying to load /run/plymouth/plymouthd.defaults
[ply-key-file.c:83]                        ply_key_file_open_file:Failed to open key file /run/plymouth/plymouthd.defaults: No such file or directory
[main.c:491]              find_distribution_default_splash:failed to load /run/plymouth/plymouthd.defaults, trying /usr/share/plymouth//
[main.c:301]                                 load_settings:Trying to load /usr/share/plymouth//plymouthd.defaults
[ply-key-file.c:171]                       ply_key_file_load_group:trying to load group Daemon
[ply-key-file.c:259]                      ply_key_file_load_groups:key file has no more groups
[main.c:315]                                 load_settings:Checking if /run/plymouth/themes/openSUSE/openSUSE.plymouth exists
[main.c:318]                                 load_settings:/run/plymouth/themes/openSUSE/openSUSE.plymouth not found, fallbacking to /usr/share/plymouth/themes/
[main.c:331]                                 load_settings:Splash delay is set to 5.000000
[main.c:342]                                 load_settings:Device timeout is set to 5.000000
[ply-key-file.c:352]                        ply_key_file_get_value:key file does not have entry for key 'DeviceScale'
[main.c:498]              find_distribution_default_splash:Distribution default theme file is '/usr/share/plymouth/themes/openSUSE/openSUSE.plymouth'
[main.c:903]           plymouth_should_show_default_splash:checking if plymouth should show default splash
[main.c:936]           plymouth_should_show_default_splash:using default splash because kernel command line has option "splash=silent"
[ply-device-manager.c:783]                 create_devices_from_terminals:checking for consoles
[ply-device-manager.c:562]                        add_consoles_from_file:opening /sys/class/tty/console/active
[ply-device-manager.c:570]                        add_consoles_from_file:reading file
[ply-device-manager.c:608]                        add_consoles_from_file:console /dev/pts/2 found!
[ply-device-manager.c:866]              ply_device_manager_watch_devices:udev support disabled, creating fallback devices
[ply-device-manager.c:697] create_devices_for_terminal_and_renderer_type:creating devices for  (renderer type: 0) (terminal: /dev/pts/2)
[ply-renderer.c:236]                      ply_renderer_open_plugin:trying to open renderer plugin /usr/lib64/plymouth/renderers/x11.so

(process:3505): Gdk-CRITICAL **: gdk_display_get_name: assertion 'GDK_IS_DISPLAY (display)' failed
Segmentation fault (core dumped)


Now I don’t know if this is helpful or whether I did it all correctly so maybe someone might like to take a look and comment.

Stuart

By changing the boot options a little more I have been able to get plymouth-debug.log file created. However it is too big to add as code and I’m not permitted to post as a file. If anyone needs to look at it let me know and I can send it.

Stuart

When you want to share lengthy text (log files, code etc), upload it to https://paste.opensuse.org/
and post the link that it provides here.

Thanks for the pointer…

The full plymouth-debug.log can be found at https://paste.opensuse.org/37719344

Stuart

Not Tumbleweed – Leap 42.2:
On this Desktop with an AMD FX™-4100 Quad-Core Processor and an AMD OLAND graphic card and an ASUS Motherboard with AMD Chip Sets:

  • The Plymouth splash behaves absolutely correctly – exactly the same as the 13.2 behaviour.

[HR][/HR]However, an AMD based Laptop with AMD Dual-Graphics also running Leap 42.2, only rarely displays the Plymouth splash and, even if the splash displays correctly or, it’s not one expected, Plymouth dumps core . . .
[HR][/HR]So, is the culprit the Dual-Graphics hardware?

Well my desktop system which fails 100% of the time is NOT dual graphics. My Intel laptop which runs Leap 42.2 and is not dual graphics runs fine with no core dumps at all.

Stuart