Bug 2458714

Summary: [abrt] plymouth: ply_event_loop_watch_for_timeout(): plymouthd killed by SIGABRT
Product: [Fedora] Fedora Reporter: Derek Enz <derekenz>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 44CC: derekenz, gnome-sig, hans, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8d532d2e4c2af04e752b9935ea9823d180686f0
Whiteboard: abrt_hash:7bd1c2b510332ad836a22590894d522b3d270321;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-05-06 19:51:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace none

Description Derek Enz 2026-04-15 16:20:01 UTC 
Description of problem:
Plymouth just randomly crashed after a reboot.

Version-Release number of selected component:
plymouth-24.004.60-24.fc44

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         plymouthd killed by SIGABRT
journald_cursor: s=6f155b21f6c24892a4d4b7ed3b7739fb;i=28b0;b=0160e0c627724be8bda33357316b4666;m=10fe52c;t=64f81987f288f;x=475b7ea94cd07948
executable:     /bin/plymouthd
cmdline:        @usr/bin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
cgroup:         0::/system.slice/plymouth-start.service
rootdir:        /
uid:            0
kernel:         6.19.10-300.fc44.x86_64
package:        plymouth-24.004.60-24.fc44
runlevel:       /bin/sh: line 1: runlevel: command not found
comment:        Plymouth just randomly crashed after a reboot.
backtrace_rating: 4
crash_function: ply_event_loop_watch_for_timeout

Truncated backtrace:
Thread no. 1 (4 frames)
 #7 ply_event_loop_watch_for_timeout at ../src/libply/ply-event-loop.c:917
 #8 ply_event_loop_handle_timeouts at ../src/libply/ply-event-loop.c:1192
 #9 ply_event_loop_process_pending_events at ../src/libply/ply-event-loop.c:1251
 #10 ply_event_loop_run at ../src/libply/ply-event-loop.c:1311


Potential duplicate: bug 1898923
Comment 1 Derek Enz 2026-04-15 16:20:05 UTC 
Created attachment 2137206 [details]
File: proc_pid_status
Comment 2 Derek Enz 2026-04-15 16:20:06 UTC 
Created attachment 2137207 [details]
File: maps
Comment 3 Derek Enz 2026-04-15 16:20:07 UTC 
Created attachment 2137208 [details]
File: limits
Comment 4 Derek Enz 2026-04-15 16:20:08 UTC 
Created attachment 2137209 [details]
File: environ
Comment 5 Derek Enz 2026-04-15 16:20:10 UTC 
Created attachment 2137210 [details]
File: open_fds
Comment 6 Derek Enz 2026-04-15 16:20:11 UTC 
Created attachment 2137211 [details]
File: mountinfo
Comment 7 Derek Enz 2026-04-15 16:20:12 UTC 
Created attachment 2137212 [details]
File: os_info
Comment 8 Derek Enz 2026-04-15 16:20:14 UTC 
Created attachment 2137213 [details]
File: cpuinfo
Comment 9 Derek Enz 2026-04-15 16:20:15 UTC 
Created attachment 2137214 [details]
File: core_backtrace
Comment 10 Derek Enz 2026-04-15 16:20:16 UTC 
Created attachment 2137215 [details]
File: dso_list
Comment 11 Derek Enz 2026-04-15 16:20:18 UTC 
Created attachment 2137216 [details]
File: backtrace
Comment 12 Derek Enz 2026-05-06 19:51:59 UTC 
As of F44 RC 1.7 it works for me.