Bug 2302344 - plymouthd crashed, causing plymouth-start.service to fail
Summary: plymouthd crashed, causing plymouth-start.service to fail
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 42
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
: 2336530 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-01 17:36 UTC by Adam Williamson
Modified: 2026-06-08 16:01 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 16:01:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2024-08-01 17:36:41 UTC
During an openQA test today, plymouthd crashed, causing plymouth-start.service to fail (the test was a check for failed services, so it failed). I don't know if this will be a consistent failure caused by a change introduced today, or if it's something periodic that might have been lurking already.

The journal shows:

Aug 01 04:02:02 fedora systemd[1]: Received SIGRTMIN+21 from PID 360 (plymouthd).
Aug 01 04:02:02 fedora kernel: fbcon: Taking over console
Aug 01 04:02:02 fedora kernel: Console: switching to colour frame buffer device 128x48
Aug 01 04:02:02 fedora realmd[1467]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Aug 01 04:02:02 fedora realmd[1467]: holding daemon: startup
Aug 01 04:02:02 fedora realmd[1467]: starting service
Aug 01 04:02:02 fedora realmd[1467]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
Aug 01 04:02:02 fedora realmd[1467]: connected to bus
Aug 01 04:02:02 fedora realmd[1467]: GLib-GIO: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
Aug 01 04:02:02 fedora realmd[1467]: released daemon: startup
Aug 01 04:02:02 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=realmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 01 04:02:02 fedora systemd[1]: Started realmd.service - Realm and Domain Configuration.
Aug 01 04:02:02 fedora realmd[1467]: claimed name on bus: org.freedesktop.realmd
Aug 01 04:02:02 fedora systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
Aug 01 04:02:02 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 01 04:02:02 fedora systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup.
Aug 01 04:02:02 fedora systemd[1]: Stopping systemd-vconsole-setup.service - Virtual Console Setup...
Aug 01 04:02:02 fedora systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
Aug 01 04:02:02 fedora systemd[1]: run-credentials-systemd\x2dvconsole\x2dsetup.service.mount: Deactivated successfully.
Aug 01 04:02:03 fedora audit[360]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:kernel_t:s0 pid=360 comm="plymouthd" exe=2F7362696E2F706C796D6F75746864202864656C6574656429 sig=6 res=1
Aug 01 04:02:03 fedora systemd-coredump[1477]: Process 360 (plymouthd) of user 0 terminated abnormally with signal 6/ABRT, processing...

The traceback:

Core was generated by `@usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-sessio'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
        tid = <optimized out>
        ret = 0
        pd = <optimized out>
        old_mask = {__val = {140732162816576}}
        ret = <optimized out>
#1  0x00007fbd8b51b793 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
No locals.
#2  0x00007fbd8b4c2d0e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
        ret = <optimized out>
#3  0x00007fbd8b4aa942 in __GI_abort () at abort.c:79
        save_stage = 1
        act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, sa_mask = {__val = {140452062545958, 94372621831376, 94372621831376, 0, 7, 0, 4, 42255093808, 0, 
              140732162816760, 18446744073709551496, 9, 94372621831360, 140732162816800, 140452062995982, 140452064470240}}, sa_flags = 1844748032, sa_restorer = 0x7ffec292bb20}
#4  0x00007fbd8b4aa85e in __assert_fail_base (fmt=0x7fbd8b65ecb0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fbd8b6c59e4 "display != NULL", 
    file=file@entry=0x7fbd8b6c3a40 "../src/libply-splash-core/ply-pixel-display.c", line=line@entry=135, 
    function=function@entry=0x7fbd8b6c5f80 <__PRETTY_FUNCTION__.1.lto_priv.2> "ply_pixel_display_unpause_updates") at assert.c:94
        str = 0x55d4d699ccd0 "<\323ԋ\321U"
        total = 4096
#5  0x00007fbd8b4bae47 in __assert_fail (assertion=assertion@entry=0x7fbd8b6c59e4 "display != NULL", file=file@entry=0x7fbd8b6c3a40 "../src/libply-splash-core/ply-pixel-display.c", 
    line=line@entry=135, function=function@entry=0x7fbd8b6c5f80 <__PRETTY_FUNCTION__.1.lto_priv.2> "ply_pixel_display_unpause_updates") at assert.c:103
No locals.
#6  0x00007fbd8b6b7bf0 in ply_pixel_display_unpause_updates (display=<optimized out>) at ../src/libply-splash-core/ply-pixel-display.c:135
        __PRETTY_FUNCTION__ = <optimized out>
#7  ply_pixel_display_unpause_updates (display=<optimized out>) at ../src/libply-splash-core/ply-pixel-display.c:133
        __PRETTY_FUNCTION__ = "ply_pixel_display_unpause_updates"
#8  0x00007fbd8b6b7dc0 in ply_boot_splash_unpause_pixel_displays (splash=0x55d4d69a0a70) at ../src/libply-splash-core/ply-boot-splash.c:493
        display = <optimized out>
        node = 0x55d4d69aa670
        node = <optimized out>
        display = <optimized out>
#9  ply_boot_splash_flush_displays (splash=0x55d4d69a0a70) at ../src/libply-splash-core/ply-boot-splash.c:503
No locals.
#10 on_new_frame (splash=0x55d4d69a0a70) at ../src/libply-splash-core/ply-boot-splash.c:513
No locals.
#11 on_new_frame (splash=0x55d4d69a0a70) at ../src/libply-splash-core/ply-boot-splash.c:508
No locals.
#12 0x00007fbd8b6df093 in ply_event_loop_handle_timeouts (loop=0x55d4d69963e0) at ../src/libply/ply-event-loop.c:1192
        next_node = <optimized out>
        watch = 0x55d4d699a4b0
        node = 0x55d4d69fc2c0
        now = 16.553295392999999
        node = <optimized out>
        now = <optimized out>
--Type <RET> for more, q to quit, c to continue without paging--c
        __PRETTY_FUNCTION__ = <optimized out>
        next_node = <optimized out>
        watch = <optimized out>
#13 ply_event_loop_process_pending_events (loop=0x55d4d69963e0) at ../src/libply/ply-event-loop.c:1251
        timeout = <optimized out>
        number_of_received_events = 0
        i = <optimized out>
        number_of_received_events = <optimized out>
        i = <optimized out>
        events = <optimized out>
        __PRETTY_FUNCTION__ = <optimized out>
        timeout = <optimized out>
        source = <optimized out>
        source = <optimized out>
        status = <optimized out>
        is_disconnected = <optimized out>
        bytes_ready = <optimized out>
        source = <optimized out>
#14 ply_event_loop_process_pending_events (loop=loop@entry=0x55d4d69963e0) at ../src/libply/ply-event-loop.c:1210
        number_of_received_events = <optimized out>
        i = <optimized out>
        __PRETTY_FUNCTION__ = "ply_event_loop_process_pending_events"
        events = {{events = 4294967295, data = {ptr = 0xffffffffffffffff, fd = -1, u32 = 4294967295, u64 = 18446744073709551615}} <repeats 64 times>}
        timeout = <optimized out>
        source = <optimized out>
        source = <optimized out>
        status = <optimized out>
        is_disconnected = <optimized out>
        bytes_ready = <optimized out>
        source = <optimized out>
#15 0x00007fbd8b6df758 in ply_event_loop_run (loop=0x55d4d69963e0) at ../src/libply/ply-event-loop.c:1311
No locals.
#16 0x000055d4b7cb044a in main (argc=<optimized out>, argv=0x7ffec292c068) at ../src/main.c:2561
        state = {loop = 0x55d4d69963e0, boot_server = 0x55d4d6999030, boot_splash = 0x0, kmsg_reader = 0x55d4d699b5a0, session = 0x55d4d699a360, boot_buffer = 0x55d4d6999330, 
          progress = 0x55d4d699b7a0, keystroke_triggers = 0x55d4d6997f50, entry_triggers = 0x55d4d6997f70, entry_buffer = 0x55d4d6997f90, messages = 0x55d4d6998fc0, 
          command_parser = 0x55d4d69962a0, mode = PLY_BOOT_SPLASH_MODE_BOOT_UP, local_console_terminal = 0x55d4d699c7c0, device_manager = 0x55d4d699bc70, deactivate_trigger = 0x0, 
          quit_trigger = 0x0, kmsg_trigger = 0x0, start_time = 2.5737814999999999, splash_delay = nan(0x8000000000000), device_timeout = 8, no_boot_log = 0, showing_details = 0, 
          system_initialized = 1, is_redirected = 0, is_attached = 0, should_be_attached = 1, should_retain_splash = 1, is_inactive = 1, is_shown = 1, should_force_details = 0, 
          should_force_default_splash = 0, splash_is_becoming_idle = 0, override_splash_path = 0x0, system_default_splash_path = 0x0, 
          distribution_default_splash_path = 0x55d4d699bc30 "/usr/share/plymouth/themes//bgrt/bgrt.plymouth", default_tty = 0x55d4b7cc725f "/dev/tty1", number_of_errors = 0}
        exit_code = <optimized out>
        should_help = false
        no_boot_log = false
        no_daemon = false
        debug = false
        ignore_serial_consoles = false
        graphical_boot = false
        attach_to_session = true
        daemon_handle = 0x55d4d6996eb0
        mode_string = 0x55d4d6996dc0 "sys-kernel-config.mount"
        kernel_command_line = 0x0
        tty = 0x0
        device_manager_flags = <optimized out>
        __func__ = "main"

Comment 1 Philippe Troin 2024-12-06 02:21:11 UTC
I'm seeing exactly the same issue on ~20% of our fleet.
Always on the same machines, but happening randomly on these set of machines.

Comment 2 Aoife Moloney 2025-02-26 13:10:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 3 Hans de Goede 2025-07-03 09:34:15 UTC
*** Bug 2336530 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Release Engineering 2026-05-06 11:52:25 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Adam Williamson 2026-05-06 18:39:50 UTC
Don't recall seeing this one lately. Letting it go EOL is probably fine.

Comment 6 Aoife Moloney 2026-06-08 16:01:02 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.