plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

[darkshvein]

Binary package hint: plymouth

Empty screen after login into Unity session! Work only right mouse button menu.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sun Apr 3 11:17:10 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: Gigabyte Technology Co., Ltd. GA-MA785G-UD3H
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=9bef9685-c9c9-4388-804f-4e008b0e40fd ro quiet splash elevator=noop vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x83cfa8 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0x0083cfa8) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_trigger_add_handler () from /lib/libply.so.2
 ?? ()
 ?? ()
 ply_event_loop_process_pending_events () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: Upgraded to natty on 2011-04-03 (1 days ago)
UserGroups:

dmi.bios.date: 09/06/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5g
dmi.board.name: GA-MA785G-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5g:bd09/06/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785G-UD3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA785G-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Apport retracing service (apport)]

StacktraceTop:
 ply_trigger_add_handler (trigger=0x0, handler=0x804a754 <ply_trigger_pull@plt>, user_data=0x95b1ae8) at ply-trigger.c:105
 on_deactivate (state=0xbfb17024, deactivate_trigger=0x95b1ae8) at main.c:940
 ply_boot_connection_on_request (connection=0x95b1cd8) at ply-boot-server.c:402
 ply_event_loop_handle_met_status_for_source (loop=0x95ac0a8) at ply-event-loop.c:1054
 ply_event_loop_process_pending_events (loop=0x95ac0a8) at ply-event-loop.c:1333

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brian Murray (brian-murray)]

This stacktrace looks very similar to bug 864430.

[Brian Murray (brian-murray)]

This is rather prevalent in raring as we can see on the ubuntu error tracker:

https://errors.ubuntu.com/bucket/?id=/sbin/plymouthd:11:ply_trigger_add_handler:on_deactivate:ply_boot_connection_on_request:ply_event_loop_handle_met_status_for_source:ply_event_loop_process_pending_events

[Doug McMahon (mc3man)]

In 13.10 if using the mir-team/system-compositor-testing/ubuntu packages this crash is again very likely to occur
(probably a good thing otherwise plymouthd is likely to run amok & max out a core