plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #554568 reported by Adalberto Cirilo Chavez Mareco
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

nn

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 3 09:09:46 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100209)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=d3a4b4ca-f21a-4bf4-bf4a-31d367c57fd2 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VGA16 VGA
SegvAnalysis:
 Segfault happened at: 0x7f145ac1409c <ply_event_loop_process_pending_events+508>: test %r12d,0x8(%r13)
 PC (0x7f145ac1409c) 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: 01/21/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SGP4510H.86A.0125.2010.0121.1927
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DP45SG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27733-402
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrSGP4510H.86A.0125.2010.0121.1927:bd01/21/2010:svn:pn:pvr:rvnIntelCorporation:rnDP45SG:rvrAAE27733-402:cvn:ct3:cvr:

Revision history for this message
Adalberto Cirilo Chavez Mareco (adalbertochavez) wrote :
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.

visibility: private → public
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.