plymouthd assert failure: plymouthd: ply-event-loop.c:352: ply_event_source_free: Assertion `ply_list_get_length (source->destinations) == 0' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
plymouthd assert failure: plymouthd: ply-event-
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu25
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
AssertionMessage: plymouthd: ply-event-
CrashCounter: 1
Date: Sun Jul 31 13:41:38 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110727)
MachineType: Acer, inc. Aspire 5600
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
__assert_fail () from /lib/i386-
?? () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/
Title: plymouthd assert failure: plymouthd: ply-event-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 06/23/06
dmi.bios.vendor: Acer
dmi.bios.version: v0.3122
dmi.board.name: Bodensee2
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5600
dmi.product.
dmi.sys.vendor: Acer, inc.
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #795413, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.