We've managed to extract a core from one of these crashes; backtrace
follows:
Core was generated by `@sbin/plymouthd --mode=boot --attach-to-session'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fd06f377f79 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x00007fd06f377f79 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007fd06f37b388 in __GI_abort () at abort.c:89
#2 0x00007fd06f370e36 in __assert_fail_base (
fmt=0x7fd06f4c24b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x7fd06f713f37 "terminal != ((void *)0)",
file=file@entry=0x7fd06f713f28 "ply-terminal.c", line=line@entry=611,
function=function@entry=0x7fd06f714860 <__PRETTY_FUNCTION__.7286>
"ply_terminal_open") at assert.c:92
#3 0x00007fd06f370ee2 in __GI___assert_fail (
assertion=assertion@entry=0x7fd06f713f37 "terminal != ((void *)0)",
file=file@entry=0x7fd06f713f28 "ply-terminal.c", line=line@entry=611,
function=function@entry=0x7fd06f714860 <__PRETTY_FUNCTION__.7286>
"ply_terminal_open") at assert.c:101
#4 0x00007fd06f70e5ff in ply_terminal_open (terminal=0x0)
at ply-terminal.c:611
#5 0x000000000040d6eb in add_display_and_keyboard_for_terminal (
terminal=0x149e900, state=0x7fff14ff8d00) at main.c:1539
#6 add_display_and_keyboard_for_console (console=0x149e8e0 "/dev/ttyS0",
null=<optimized out>, state=0x7fff14ff8d00) at main.c:1953
#7 0x00007fd06f921f63 in ply_hashtable_foreach (
hashtable=hashtable@entry=0x149e710,
func=func@entry=0x40d650 <add_display_and_keyboard_for_console>,
user_data=user_data@entry=0x7fff14ff8d00) at ply-hashtable.c:280
#8 0x000000000040c943 in check_for_consoles (
state=state@entry=0x7fff14ff8d00, default_tty=<optimized out>,
should_add_displays=should_add_displays@entry=true) at main.c:2158
#9 0x000000000040d0ec in on_show_splash (state=0x7fff14ff8d00) at main.c:916
#10 0x00000000004065d9 in ply_boot_connection_on_request (connection=0x149e4d0)
at ply-boot-server.c:702
#11 0x00007fd06f91ee76 in ply_event_loop_handle_met_status_for_source (
status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x149e5b0, loop=0x1497150)
at ply-event-loop.c:1060
#12 ply_event_loop_process_pending_events (loop=loop@entry=0x1497150)
at ply-event-loop.c:1336
#13 0x00007fd06f91f620 in ply_event_loop_run (loop=0x1497150)
at ply-event-loop.c:1368
#14 0x0000000000404c3d in main (argc=<optimized out>, argv=<optimized out>)
at main.c:2563
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160079
Title:
plymouth aborts in cloud images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1160079/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
