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
This crash occurred on first boot after upgrading from karmic to lucid (beta2).
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Fri Apr 9 14:57:09 2010
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: PINNACLE MICRO PROLINE DQ35JOE
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
Segfault happened at: 0x7f76241d109c <ply_event_
PC (0x7f76241d109c) 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: 08/07/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JOQ3510J.
dmi.board.
dmi.board.name: DQ35JO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD82085-801
dmi.chassis.type: 3
dmi.chassis.
dmi.modalias: dmi:bvnIntelCor
dmi.product.name: PROLINE DQ35JOE
dmi.sys.vendor: PINNACLE MICRO
description: | updated |
visibility: | private → public |
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.