plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #979583 reported by giorgio130
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happens as soon as I turn the machine on.
I don't think it is a duplicate since most of them say "fix released", I made all updates so I think this is new.
I'm on precise.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu29
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Thu Apr 12 08:11:27 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=91306d31-6c56-4c78-bd6d-ebd57ddc3b3c ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=91306d31-6c56-4c78-bd6d-ebd57ddc3b3c ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f73c3d2a514 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7f73c3d2a514) 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 () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: Upgraded to precise on 2012-04-11 (0 days ago)
UserGroups:

dmi.bios.date: 07/08/2008
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.04
dmi.board.name: JHL90
dmi.board.vendor: COMPAL
dmi.board.version: REFERENCE
dmi.chassis.type: 1
dmi.chassis.vendor: COMPAL
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.04:bd07/08/2008:svnCOMPAL:pn:pvr:rvnCOMPAL:rnJHL90:rvrREFERENCE:cvnCOMPAL:ct1:cvrN/A:
dmi.sys.vendor: COMPAL

Revision history for this message
giorgio130 (gm89) 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 this software better. This particular crash has already been reported and is a duplicate of bug #969667, 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
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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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