plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
plymouthd crashed with SIGSEGV in ply_event_
This may be a duplicate, but please check as I am not sure. Thank You...
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.2.0-10-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDmesg:
[ 21.656085] init: plymouth-stop pre-start process (1037) terminated with status 1
[ 27.296025] eth0: no IPv6 routers present
Date: Thu Jan 26 16:20:47 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120111)
MachineType: Dell Computer Corporation Dimension 3000
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: 0xf195b7 <ply_event_
PC (0x00f195b7) ok
source "%ecx" ok
destination "0x4(%esi)" (0x00000004) 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/i386-
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_event_
UpgradeStatus: Upgraded to precise on 2012-01-12 (14 days ago)
UserGroups:
dmi.bios.date: 01/05/2006
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A03
dmi.board.name: 0TC667
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComp
dmi.product.name: Dimension 3000
dmi.sys.vendor: Dell Computer Corporation
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 #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.