plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #950839 reported by noxified
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

ubuntu 12.04 beta 2 distrib

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
Date: Fri Mar 9 16:10:33 2012
DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228)
MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5515
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae root=UUID=bf311fc3-3428-4b84-b4d7-98a0f501df03 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-18-generic-pae root=UUID=bf311fc3-3428-4b84-b4d7-98a0f501df03 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb77a95b7 <ply_event_loop_process_pending_events+455>: test %ecx,0x4(%esi)
 PC (0xb77a95b7) 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/xubuntu-text/xubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/30/07
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.10
dmi.board.name: Z17M
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: V1.08
dmi.chassis.asset.tag: User Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvnPhoenix:bvrV1.10:bd11/30/07:svnFUJITSUSIEMENS:pnESPRIMOMobileV5515:pvrV1.08:rvnFUJITSUSIEMENS:rnZ17M:rvrV1.08:cvnFUJITSUSIEMENS:ct1:cvrV1.08:
dmi.product.name: ESPRIMO Mobile V5515
dmi.product.version: V1.08
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
noxified (n0xified) 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.

affects: ubuntu → plymouth (Ubuntu)
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.