plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
just starting
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
CurrentDmesg:
[ 11.063635] ppdev: user-space parallel port driver
[ 21.050044] eth1: no IPv6 routers present
[ 72.320063] Clocksource tsc unstable (delta = -277587259 ns)
Date: Sat Apr 3 00:18:36 2010
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: Dell Inc. Inspiron 1501
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
SegvAnalysis:
Segfault happened at: 0x7f7d6f69e09c <ply_event_
PC (0x7f7d6f69e09c) 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/libc.so.6
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_event_
UserGroups:
dmi.bios.date: 12/07/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.3
dmi.board.name: 0UW744
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1501
dmi.product.
dmi.sys.vendor: Dell 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 #553745, 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.