Created attachment 122972 [details] coredump In my openSUSE Tumbleweed installation, plymouthd always coredumps during startup. Backtrace (core attached): #0 ply_event_loop_get_destination_from_fd_watch (loop=0x7974742f7665642f, watch=0x21) at ply-event-loop.c:449 #1 0x00007f0d1675920b in ply_event_loop_stop_watching_fd (loop=0x7974742f7665642f, watch=0x21) at ply-event-loop.c:750 #2 0x00007f0d165458f7 in ply_terminal_close () from /usr/lib64/libply-splash-core.so.4 #3 0x00007f0d1675cc53 in ply_hashtable_foreach (hashtable=0x180f8e0, func=0x7f0d16545870 <ply_terminal_close>, user_data=0x180ff20) at ply-hashtable.c:268 #4 0x000000000040c050 in quit_splash (state=state@entry=0x7ffd0872a000) at main.c:1064 #5 0x000000000040c8af in on_boot_splash_idle (state=0x7ffd0872a000) at main.c:1196 #6 0x00007f0d16759d2a in ply_event_loop_handle_timeouts (loop=0x180a150) at ply-event-loop.c:1192 #7 ply_event_loop_process_pending_events (loop=loop@entry=0x180a150) at ply-event-loop.c:1251 #8 0x00007f0d1675a340 in ply_event_loop_run (loop=0x180a150) at ply-event-loop.c:1310 #9 0x0000000000405454 in main (argc=<optimized out>, argv=<optimized out>) at main.c:2233 plymouth package version: 0.9.2-2.1
Created attachment 122973 [details] core.plymouthd..xz Added coredump with binary content type
After looking at the sources it seems like the offending code was added or triggered by openSUSE patches. I reported it in their issue tracker: https://bugzilla.opensuse.org/show_bug.cgi?id=975879
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/plymouth/plymouth/issues/61.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.