plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #559207 reported by PrivateUser132781
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Fri Apr 9 14:57:09 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: PINNACLE MICRO PROLINE DQ35JOE
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=51b3ec00-b9c0-4bdd-b888-bd1577a26d69 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
 Segfault happened at: 0x7f76241d109c <ply_event_loop_process_pending_events+508>: test %r12d,0x8(%r13)
 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_loop_process_pending_events ()
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UserGroups:

dmi.bios.date: 08/07/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JOQ3510J.86A.0942.2008.0807.1958
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DQ35JO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD82085-801
dmi.chassis.type: 3
dmi.chassis.version: UATX
dmi.modalias: dmi:bvnIntelCorp.:bvrJOQ3510J.86A.0942.2008.0807.1958:bd08/07/2008:svnPINNACLEMICRO:pnPROLINEDQ35JOE:pvr:rvnIntelCorporation:rnDQ35JO:rvrAAD82085-801:cvn:ct3:cvrUATX:
dmi.product.name: PROLINE DQ35JOE
dmi.sys.vendor: PINNACLE MICRO

Revision history for this message
PrivateUser132781 (privateuser132781-deactivatedaccount) wrote :
description: updated
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.