plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Oct 7 20:14:12 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110919)
MachineType: Acer Aspire 1830
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f483d0e8504 <ply_event_
PC (0x7f483d0e8504) ok
source "%r12d" ok
destination "0x8(%r13)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_event_
ply_event_loop_run () from /lib/libply.so.2
?? ()
__libc_start_main () from /lib/x86_
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_event_
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (11 days ago)
UserGroups:
dmi.bios.date: 07/09/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.14
dmi.board.
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Aspire 1830
dmi.product.
dmi.sys.vendor: Acer
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 #849414, 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.