Bug 2383662

Summary: [abrt] plymouth: ply_terminal_unlock(): plymouthd killed by SIGABRT
Product: [Fedora] Fedora Reporter: jazzjackrabbit6163+redhatbugzilla
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: gnome-sig, hdegoede, jazzjackrabbit6163+redhatbugzilla, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8d251ce4d8b9d446f716ccd19107d6836fd832c
Whiteboard: abrt_hash:574b9daa81d8b65c9eaab36830fe990e7bf56805;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:54:48 UTC 
Version-Release number of selected component:
plymouth-24.004.60-19.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         plymouthd killed by SIGABRT
journald_cursor: s=5ce2dea471794573a965290272e01b53;i=13fe2;b=e481eaa11f294f7b87533489635d31af;m=db599b;t=639f5a7d996bf;x=dfb9de0c53b18bc6
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.15.5-200.fc42.x86_64
package:        plymouth-24.004.60-19.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: ply_terminal_unlock

Truncated backtrace:
Thread no. 1 (12 frames)
 #6 ply_terminal_unlock at ../src/libply-splash-core/ply-terminal.c:205
 #7 ply_terminal_set_unbuffered_input at ../src/libply-splash-core/ply-terminal.c:242
 #8 close_input_source at ../src/plugins/renderers/drm/plugin.c:1977
 #9 ply_renderer_close_input_source at ../src/libply-splash-core/ply-renderer.c:459
 #10 ply_keyboard_stop_watching_for_renderer_input at ../src/libply-splash-core/ply-keyboard.c:402
 #11 ply_keyboard_stop_watching_for_input at ../src/libply-splash-core/ply-keyboard.c:491
 #12 ply_device_manager_deactivate_keyboards at ../src/libply-splash-core/ply-device-manager.c:1432
 #13 on_deactivate at ../src/main.c:1386
 #14 ply_boot_connection_on_request at ../src/ply-boot-server.c:515
 #15 ply_event_loop_handle_met_status_for_source at ../src/libply/ply-event-loop.c:1040
 #16 ply_event_loop_process_pending_events at ../src/libply/ply-event-loop.c:1279
 #17 ply_event_loop_run at ../src/libply/ply-event-loop.c:1311
Comment 1 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:54:54 UTC 
Created attachment 2098337 [details]
File: proc_pid_status
Comment 2 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:54:55 UTC 
Created attachment 2098338 [details]
File: maps
Comment 3 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:54:57 UTC 
Created attachment 2098339 [details]
File: limits
Comment 4 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:54:58 UTC 
Created attachment 2098340 [details]
File: environ
Comment 5 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:00 UTC 
Created attachment 2098341 [details]
File: open_fds
Comment 6 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:02 UTC 
Created attachment 2098342 [details]
File: mountinfo
Comment 7 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:04 UTC 
Created attachment 2098343 [details]
File: os_info
Comment 8 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:06 UTC 
Created attachment 2098344 [details]
File: cpuinfo
Comment 9 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:08 UTC 
Created attachment 2098345 [details]
File: core_backtrace
Comment 10 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:10 UTC 
Created attachment 2098346 [details]
File: dso_list
Comment 11 jazzjackrabbit6163+redhatbugzilla 2025-07-26 20:55:13 UTC 
Created attachment 2098347 [details]
File: backtrace
Comment 12 Nexcool 2025-08-01 13:33:12 UTC 
Using Qutebrowser in chatgpt.  Then i got this error. 


reporter:       libreport-2.17.15
type:           CCpp
reason:         plymouthd killed by SIGABRT
journald_cursor: s=c545112a7e784d10acb0086e0cdadc1a;i=9079;b=ccf7a840770449b5a59038ba2c50cbff;m=8051d8;t=63a5040f083a3;x=349fcf7dcc33f81d
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.15.6-200.fc42.x86_64
package:        plymouth-24.004.60-19.fc42
runlevel:       unknown
backtrace_rating: 4
crash_function: ply_terminal_unlock
comment:        Using Qutebrowser in chatgpt.  Then i got this error.
Comment 13 Fedora Release Engineering 2026-05-06 13:38:40 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.