plymouthd crashed with SIGSEGV in ply_list_get_first_node()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
Ubuntu Natty 11.04
Plymouth 0.8.2-2ubuntu18
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu18
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Mon Mar 21 12:45:30 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110320)
MachineType: ASUSTeK Computer Inc. F9E
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xf87377 <ply_list_
PC (0x00f87377) 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_list_
ply_event_loop_run () from /lib/libply.so.2
?? ()
__libc_start_main () from /lib/i386-
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_list_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/01/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 204
dmi.board.
dmi.board.name: F9E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: F9E
dmi.product.
dmi.sys.vendor: ASUSTeK Computer 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 #723801, 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.