plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #931623 reported by Hilmar Dageförde
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just upgraded to the newest kernel 3.2.015. The crash happened when I opened the software center.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5
Uname: Linux 3.2.0-15-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Mon Feb 13 20:08:00 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120114)
MachineType: Hewlett-Packard HP Mini 110-1000
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-15-generic-pae root=UUID=e1207187-6d67-4268-9741-4e93954bf708 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-15-generic-pae root=UUID=e1207187-6d67-4268-9741-4e93954bf708 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb76d35b7 <ply_event_loop_process_pending_events+455>: test %ecx,0x4(%esi)
 PC (0xb76d35b7) 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-02-07 (5 days ago)
UserGroups:

dmi.bios.date: 09/02/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 308F0 Ver. F.16
dmi.board.name: 308F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.10
dmi.chassis.asset.tag: CNU9315ZSD
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.16:bd09/02/2009:svnHewlett-Packard:pnHPMini110-1000:pvr03A8100000000000100300000:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Mini 110-1000
dmi.product.version: 03A8100000000000100300000
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Hilmar Dageförde (hildageforde) 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 #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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-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.