plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

[Terrapin Station]

none

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 1 17:31:00 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110922)
MachineType: Dell Inc. Studio XPS 1640
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=17405760-c00f-41ef-8d80-b2241842c286 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=17405760-c00f-41ef-8d80-b2241842c286 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fe9b467a3ab <ply_trigger_add_handler+43>: mov (%rbx),%rdi
 PC (0x7fe9b467a3ab) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/19/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0U785D
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2009:svnDellInc.:pnStudioXPS1640:pvrA123:rvnDellInc.:rn0U785D:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Studio XPS 1640
dmi.product.version: A123
dmi.sys.vendor: Dell Inc.

[Apport retracing service (apport)]

StacktraceTop:
 ply_trigger_add_handler (trigger=0x0, handler=0x4037f0 <ply_trigger_pull@plt>, user_data=0x25153e0) at ply-trigger.c:105
 ply_boot_connection_on_request (connection=0x251ff80) at ply-boot-server.c:402
 ply_event_loop_handle_met_status_for_source (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x2516440, loop=0x250e140) at ply-event-loop.c:1054
 ply_event_loop_process_pending_events (loop=0x250e140) at ply-event-loop.c:1333
 ply_event_loop_run (loop=0x250e140) at ply-event-loop.c:1365

[Launchpad Janitor (janitor)]

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

[Msirdian (arena7)]

this happened after upgrade

[Brian Murray (brian-murray)]

This stacktrace looks very similar to bug 750405.

[Stinger (e-mindahl)]

Still present in Quantal

[Wajih Letaief (mawale)]

Still present in Quantal with GDM and not lightdm (Gnome not Unity)

[Uni (yubo)]

Observed this crash on the Gnome shell version of 13.04 (still in development).
Saw the bug report message just after logging.
Not a critical bug (I can continue to use the system without any other visible impact)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:
http://packages.qa.ubuntu.com/qatracker/reports/bugs/864430

[Carla Sella (carla-sella)]

Happened to me a couple of times after reboot and having MIR installed from PPA for testing.
See bug #1196233 marked as duplicate of this one.
My hardware: http://pastebin.com/4mzGN7By.

[DonnieD (donnied)]

Same as Carla Sella here.
bug #1196670 also marked as dublicate
My hardware http://pastebin.com/SXa9NTN9
Also with MIR from PPA

[AO (aofrl10n)]

I'm experiecing this on a fully updated 13.10 amd64.

[Pedro Borges (funakyfunaky)]

I'm experiencing this after logging in 13.10. Full release with latest updates.

[Bastian Mattes (gartenriese)]

Happend to me at first boot after a fresh installation of 13.10

[Tomek (nomattr)]

I always get this bug on startup. I don't see any problems, though.