plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This happens as soon as I turn the machine on.
I don't think it is a duplicate since most of them say "fix released", I made all updates so I think this is new.
I'm on precise.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu29
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Thu Apr 12 08:11:27 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f73c3d2a514 <ply_event_
PC (0x7f73c3d2a514) 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 precise on 2012-04-11 (0 days ago)
UserGroups:
dmi.bios.date: 07/08/2008
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.04
dmi.board.name: JHL90
dmi.board.vendor: COMPAL
dmi.board.version: REFERENCE
dmi.chassis.type: 1
dmi.chassis.vendor: COMPAL
dmi.chassis.
dmi.modalias: dmi:bvnCOMPAL:
dmi.sys.vendor: COMPAL
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #969667, 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.