20241119 Plymouth segfault
Today I updated several TW machines to 20241119 ( 2 physical machines and 3 vms ). All the updates when fine. When I rebooted one of the physical machines after selecting the grub entry to boot, the cursor in the left corner of a blank screen with no messages and roughly 30 seconds later the login GUI is displayed. Looking at the journal I found that plymouth is terminating with a segfault. It does not happen all the time but it does happen most times. If I do a shutdown/poweroff and then poweron sometimes it doesn't happen. If I do a reboot, then it seems to happen ever time. Is this a known issue ? Here's journal: Nov 22 14:04:26 systemd-coredump[1514]: Process 714 (plymouthd) of user 0 terminated abnormally with signal 11/SEGV, processing... Nov 22 14:04:26 systemd[1]: Created slice Slice /system/drkonqi-coredump-processor. Nov 22 14:04:26 systemd[1]: Created slice Slice /system/systemd-coredump. Nov 22 14:04:26 systemd[1]: Starting Load Kernel Module dm_mod... Nov 22 14:04:26 systemd[1]: Starting Load Kernel Module efi_pstore... Nov 22 14:04:26 systemd[1]: Starting Load Kernel Module loop... Nov 22 14:04:26 systemd[1]: Set Up Additional Binary Formats was skipped because no trigger condition checks were met. Nov 22 14:04:26 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLoca> Nov 22 14:04:26 systemd[1]: Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). Nov 22 14:04:26 systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var). Nov 22 14:04:26 systemd[1]: Create System Users was skipped because no trigger condition checks were met. Nov 22 14:04:26 systemd[1]: First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). Nov 22 14:04:26 systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). Nov 22 14:04:26 systemd[1]: Save Transient machine-id to Disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id). Nov 22 14:04:26 systemd[1]: Update is Completed was skipped because no trigger condition checks were met. Nov 22 14:04:26 systemd[1]: Started Process Core Dump (PID 1514/UID 0). Nov 22 14:04:26 systemd[1]: modprobe@dm_mod.service: Deactivated successfully. Nov 22 14:04:26 systemd[1]: Finished Load Kernel Module dm_mod. Nov 22 14:04:26 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. Nov 22 14:04:26 systemd[1]: Finished Load Kernel Module efi_pstore. Nov 22 14:04:26 systemd[1]: modprobe@loop.service: Deactivated successfully. Nov 22 14:04:26 systemd[1]: Finished Load Kernel Module loop. Nov 22 14:04:26 systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). Nov 22 14:04:26 systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met. Nov 22 14:04:26 systemd-coredump[1518]: [??] Process 714 (plymouthd) of user 0 dumped core. Stack trace of thread 714: #0 0x00007f36a76e15c4 ply_input_device_get_keymap (libply-splash-core.so.5 + 0xd5c4) #1 0x00007f36a72a85a0 n/a (drm.so + 0xa5a0) #2 0x00007f36a5390c36 ply_keymap_icon_new (libply-splash-graphics.so.5 + 0x9c36) #3 0x00007f36a6ff7b0e n/a (two-step.so + 0xab0e) #4 0x00007f36a76e3a17 ply_boot_splash_add_pixel_display (libply-splash-core.so.5 + 0xfa17) #5 0x000055e4cd456274 n/a (plymouthd + 0xe274) #6 0x000055e4cd45764a n/a (plymouthd + 0xf64a) #7 0x000055e4cd45b8f8 n/a (plymouthd + 0x138f8) #8 0x00007f36a76e51a0 n/a (libply-splash-core.so.5 + 0x111a0) #9 0x00007f36a76e8499 n/a (libply-splash-core.so.5 + 0x14499) #10 0x00007f36a76ef15f n/a (libply-splash-core.so.5 + 0x1b15f) #11 0x00007f36a76e53db n/a (libply-splash-core.so.5 + 0x113db) #12 0x00007f36a76ea243 n/a (libply-splash-core.so.5 + 0x16243) #13 0x00007f36a770b0a8 ply_event_loop_process_pending_events (libply.so.5 + 0x100a8) #14 0x00007f36a770b578 ply_event_loop_run (libply.so.5 + 0x10578) #15 0x000055e4cd44e571 main (plymouthd + 0x6571) #16 0x00007f36a74ec2ae __libc_start_call_main (libc.so.6 + 0x2a2ae) #17 0x00007f36a74ec379 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a379) #18 0x000055e4cd44fa65 _start (plymouthd + 0x7a65) ELF object binary architecture: AMD x86-64 Nov 22 14:04:26 systemd[1]: systemd-coredump@0-1514-0.service: Deactivated successfully. Nov 22 14:04:26 plymouth[1141]: error: unexpectedly disconnected from boot status daemon Nov 22 14:04:26 plymouth[1425]: error: unexpectedly disconnected from boot status daemon Nov 22 14:04:26 systemd[1]: Started Show Plymouth Boot Screen. Nov 22 14:04:26 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV Nov 22 14:04:26 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. Nov 22 14:04:26 systemd[1]: Finished Tell Plymouth To Write Out Runtime Data. -- Regards, Joe
On Fri, Nov 22, 2024 at 10:16 PM Joe Salmeri <jmscdba@gmail.com> wrote:
Today I updated several TW machines to 20241119 ( 2 physical machines and 3 vms ).
All the updates when fine.
When I rebooted one of the physical machines after selecting the grub entry to boot, the cursor in the left corner of a blank screen with no messages and roughly 30 seconds later the login GUI is displayed.
Looking at the journal I found that plymouth is terminating with a segfault.
I had the same behavior on the boot I did today. Haven't tried again and already upgraded to 20241121 snapshot, don't know although if it solves it (haven't rebooted yet).
On 11/22/24 3:50 PM, Stratos Zolotas wrote:
On Fri, Nov 22, 2024 at 10:16 PM Joe Salmeri <jmscdba@gmail.com> wrote:
Today I updated several TW machines to 20241119 ( 2 physical machines and 3 vms ).
All the updates when fine.
When I rebooted one of the physical machines after selecting the grub entry to boot, the cursor in the left corner of a blank screen with no messages and roughly 30 seconds later the login GUI is displayed.
Looking at the journal I found that plymouth is terminating with a segfault.
I had the same behavior on the boot I did today. Haven't tried again and already upgraded to 20241121 snapshot, don't know although if it solves it (haven't rebooted yet).
Thanks for that information, so I'm not alone in the seeing the issue. It seems to happen pretty much with any reboot, whereas with shutdown/poweroff/poweron it has happened about 50% of the time. It looks like 20241121 has the same version of plymouth as 20241119. FWIW, I went with 20241119 because 20241121 had 16 few tests that passed QA. https://openqa.opensuse.org/group_overview/1?limit_builds=25 -- Regards, Joe
On Fri, Nov 22, 2024 at 11:12 PM Joe Salmeri <jmscdba@gmail.com> wrote:
It seems to happen pretty much with any reboot, whereas with shutdown/poweroff/poweron it has happened about 50% of the time.
It looks like 20241121 has the same version of plymouth as 20241119.
Can confirm that it happens also with 20241121. Boot today (after shutdown last night) had the same behavior.
participants (2)
-
Joe Salmeri
-
Stratos Zolotas