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)
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.
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.
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?
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'.
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’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.
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
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.
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.
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.