plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #960924 reported by pinchface
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Crashed after reboot, it ALWAYS crashes whenever the PC is turned on.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
Uname: Linux 3.2.0-19-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Thu Mar 15 10:57:51 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: OEM OEM
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic-pae root=UUID=0d78bbe0-36ab-46e8-8b9f-16e36ad3dac5 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic-pae root=UUID=0d78bbe0-36ab-46e8-8b9f-16e36ad3dac5 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb78305b7 <ply_event_loop_process_pending_events+455>: test %ecx,0x4(%esi)
 PC (0xb78305b7) ok
 source "%ecx" ok
 destination "0x4(%esi)" (0x00000004) 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/i386-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-03-17 (4 days ago)
UserGroups:

dmi.bios.date: 07/30/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: G31MX Series
dmi.board.vendor: Foxconn
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/30/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM:
dmi.product.name: OEM
dmi.product.version: OEM
dmi.sys.vendor: OEM

Revision history for this message
pinchface (pinchface) wrote :
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 this software better. This particular crash has already been reported and is a duplicate of bug #849414, 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-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Mo Z (zmau1962) wrote :

Funny Story :

I had this bug infinite number of times. I was not able to work at all. The system would get to log-in window and crash after a few seconds. Once I was able to work a whole minuet before restart.....

In the following link I saw a comment which told me that this is a consequence of a race between two drivers https://bugs.freedesktop.org/show_bug.cgi?id=48894

So, I pulled out the Ethernet cable, and the problem disappeared. After the system is UP, I can re-connect the Ethernet, and there is no problem.....

More information : I am working with Ubuntu 12.04 on an Ivy Bridge machine....

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.