Hi, I've the same issue with plymouth 0.8.3-20 and systemd 37-1.
Here a backtrace. Cheers Laurent Bigonville #0 0x00007fa9aff82475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007fa9aff856f0 in *__GI_abort () at abort.c:92 #2 0x00007fa9aff7b621 in *__GI___assert_fail (assertion=0x7fa9b097191e "keyboard != ((void *)0)", file=<optimized out>, line=384, function=0x7fa9b0971a00 "ply_keyboard_watch_for_input") at assert.c:81 #3 0x00007fa9b096a898 in ply_keyboard_watch_for_input (keyboard=0x0) at ply-keyboard.c:384 #4 0x00000000004071bf in start_boot_splash (state=0x7fff6186b590, theme_path=<optimized out>) at main.c:1452 #5 0x00000000004089ef in show_detailed_splash (state=0x7fff6186b590) at main.c:199 #6 0x000000000040944d in toggle_between_splash_and_details (state=0x7fff6186b590) at main.c:1137 #7 0x0000000000409500 in dump_details_and_quit_splash (state=0x7fff6186b590) at main.c:788 #8 0x0000000000404f20 in ply_boot_connection_on_request (connection=0xab5d30) at ply-boot-server.c:592 #9 0x00007fa9b0b7c906 in ply_event_loop_handle_met_status_for_source (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0xab5ad0, loop=0xab2140) at ply-event-loop.c:1054 #10 ply_event_loop_process_pending_events (loop=0xab2140) at ply-event-loop.c:1332 #11 0x00007fa9b0b7d1b0 in ply_event_loop_run (loop=0xab2140) at ply-event-loop.c:1364 #12 0x00000000004045fd in main (argc=<optimized out>, argv=<optimized out>) at main.c:1963 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
