Bug 2368186 - [abrt] plymouth: ply_terminal_set_disabled_input(): plymouthd killed by SIGSEGV
Summary: [abrt] plymouth: ply_terminal_set_disabled_input(): plymouthd killed by SIGSEGV
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 42
Hardware: x86_64
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:be872d9e947d3b36bc861b7e78f...
: 2365419 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-23 13:01 UTC by Ural Safak
Modified: 2025-07-07 00:50 UTC (History)
6 users (show)

Fixed In Version: plymouth-24.004.60-19.fc43 plymouth-24.004.60-19.fc42
Clone Of:
Environment:
Last Closed: 2025-07-03 22:20:45 UTC
Type: ---
Embargoed:
hdegoede: mirror+


Attachments (Terms of Use)
File: proc_pid_status (1.44 KB, text/plain)
2025-05-23 13:01 UTC, Ural Safak
no flags Details
File: maps (3.97 KB, text/plain)
2025-05-23 13:01 UTC, Ural Safak
no flags Details
File: limits (1.29 KB, text/plain)
2025-05-23 13:01 UTC, Ural Safak
no flags Details
File: environ (284 bytes, text/plain)
2025-05-23 13:01 UTC, Ural Safak
no flags Details
File: open_fds (4.10 KB, text/plain)
2025-05-23 13:01 UTC, Ural Safak
no flags Details
File: mountinfo (3.30 KB, text/plain)
2025-05-23 13:02 UTC, Ural Safak
no flags Details
File: os_info (754 bytes, text/plain)
2025-05-23 13:02 UTC, Ural Safak
no flags Details
File: cpuinfo (3.19 KB, text/plain)
2025-05-23 13:02 UTC, Ural Safak
no flags Details
File: core_backtrace (7.05 KB, text/plain)
2025-05-23 13:02 UTC, Ural Safak
no flags Details
File: dso_list (484 bytes, text/plain)
2025-05-23 13:02 UTC, Ural Safak
no flags Details
File: backtrace (30.66 KB, text/plain)
2025-05-23 13:02 UTC, Ural Safak
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1764 0 None None None 2025-07-01 08:33:10 UTC

Description Ural Safak 2025-05-23 13:01:49 UTC
Version-Release number of selected component:
plymouth-24.004.60-18.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         plymouthd killed by SIGSEGV
journald_cursor: s=8cee98524a274f5692606ccf31aecc31;i=8342;b=cc944791651341668c766657cd693777;m=22654707;t=635ae057ca870;x=6405fda1bf7a7d1a
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.14.6-300.fc42.x86_64
package:        plymouth-24.004.60-18.fc42
runlevel:       unknown
backtrace_rating: 4
crash_function: ply_terminal_set_disabled_input

Truncated backtrace:
Thread no. 1 (15 frames)
 #0 ply_terminal_set_disabled_input at ../src/libply-splash-core/ply-terminal.c:335
 #1 watch_input_device at ../src/plugins/renderers/drm/plugin.c:1899
 #2 watch_input_devices at ../src/plugins/renderers/drm/plugin.c:1911
 #3 open_input_source at ../src/plugins/renderers/drm/plugin.c:1925
 #4 ply_renderer_open_input_source at ../src/libply-splash-core/ply-renderer.c:422
 #5 ply_keyboard_watch_for_renderer_input at ../src/libply-splash-core/ply-keyboard.c:378
 #6 ply_keyboard_watch_for_input at ../src/libply-splash-core/ply-keyboard.c:470
 #8 create_devices_for_terminal_and_renderer_type at ../src/libply-splash-core/ply-device-manager.c:1181
 #9 create_devices_for_udev_device at ../src/libply-splash-core/ply-device-manager.c:425
 #10 on_drm_udev_add_or_change at ../src/libply-splash-core/ply-device-manager.c:522
 #11 process_udev_add_or_change_events at ../src/libply-splash-core/ply-device-manager.c:596
 #12 on_udev_event at ../src/libply-splash-core/ply-device-manager.c:652
 #13 ply_event_loop_handle_met_status_for_source at ../src/libply/ply-event-loop.c:1040
 #14 ply_event_loop_process_pending_events at ../src/libply/ply-event-loop.c:1279
 #15 ply_event_loop_run at ../src/libply/ply-event-loop.c:1311

Comment 1 Ural Safak 2025-05-23 13:01:53 UTC
Created attachment 2091215 [details]
File: proc_pid_status

Comment 2 Ural Safak 2025-05-23 13:01:55 UTC
Created attachment 2091216 [details]
File: maps

Comment 3 Ural Safak 2025-05-23 13:01:56 UTC
Created attachment 2091217 [details]
File: limits

Comment 4 Ural Safak 2025-05-23 13:01:57 UTC
Created attachment 2091218 [details]
File: environ

Comment 5 Ural Safak 2025-05-23 13:01:59 UTC
Created attachment 2091219 [details]
File: open_fds

Comment 6 Ural Safak 2025-05-23 13:02:00 UTC
Created attachment 2091220 [details]
File: mountinfo

Comment 7 Ural Safak 2025-05-23 13:02:01 UTC
Created attachment 2091221 [details]
File: os_info

Comment 8 Ural Safak 2025-05-23 13:02:03 UTC
Created attachment 2091222 [details]
File: cpuinfo

Comment 9 Ural Safak 2025-05-23 13:02:04 UTC
Created attachment 2091223 [details]
File: core_backtrace

Comment 10 Ural Safak 2025-05-23 13:02:05 UTC
Created attachment 2091224 [details]
File: dso_list

Comment 11 Ural Safak 2025-05-23 13:02:07 UTC
Created attachment 2091225 [details]
File: backtrace

Comment 12 hayetmd 2025-06-18 08:15:20 UTC
 I have hybrid graphics setup. I have nvidia 1650 graphics card and intel gpu. 
i have forced to use xorg and remove wayland. system was becoming inresponsive. so i forced the system to load both gpu, and that fixed that problem. then i installed steam, and steam was causing the whole system to log out. Then i modified the steam to use nvidia while opening , that solved steam problem. Then everytime i restart i get this error message.


reporter:       libreport-2.17.15
type:           CCpp
cmdline:        @usr/bin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
uid:            0
kernel:         6.14.11-300.fc42.x86_64
reason:         plymouthd killed by SIGSEGV
executable:     /bin/plymouthd
runlevel:       unknown
crash_function: ply_terminal_set_disabled_input
cgroup:         0::/system.slice/plymouth-start.service
package:        plymouth-24.004.60-18.fc42
journald_cursor: s=2452bc3939254dc78b203c32fa132de9;i=76b;b=b2d68e22aa8c4fd9a7dbc6db4fe512d0;m=564dea;t=637d42b36b4bd;x=bcd287e21bb53ac7
backtrace_rating: 4
rootdir:        /

Comment 13 Hans de Goede 2025-06-18 10:35:14 UTC
*** Bug 2336530 has been marked as a duplicate of this bug. ***

Comment 14 Hans de Goede 2025-06-19 20:34:08 UTC
*** Bug 2365419 has been marked as a duplicate of this bug. ***

Comment 15 Hans de Goede 2025-07-01 21:33:19 UTC
This should be fixed by this upstream commit:

https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/d20b1be527817c21500c3daa4dfdd0e9c7

I'm working on preparing a plymouth update addressing several issues including this one.

Comment 16 Fedora Update System 2025-07-03 20:54:13 UTC
FEDORA-2025-bea98bd9ab (plymouth-24.004.60-19.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-bea98bd9ab

Comment 17 Fedora Update System 2025-07-03 22:20:45 UTC
FEDORA-2025-bea98bd9ab (plymouth-24.004.60-19.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2025-07-04 09:01:06 UTC
FEDORA-2025-84de48bce5 (plymouth-24.004.60-19.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-84de48bce5

Comment 19 Fedora Update System 2025-07-05 15:47:13 UTC
FEDORA-2025-84de48bce5 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-84de48bce5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-84de48bce5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 20 Fedora Update System 2025-07-07 00:50:18 UTC
FEDORA-2025-84de48bce5 (plymouth-24.004.60-19.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


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