plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #923054 reported by nadasjozef@freemail.hu on 2012-01-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

No.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic-pae 3.2.1
Uname: Linux 3.2.0-11-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Jan 21 19:32:18 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120108)
MachineType: VIA VN800
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic-pae root=UUID=09a753dc-3989-4378-84e1-6123e18f461a ro quiet noapic splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic-pae root=UUID=09a753dc-3989-4378-84e1-6123e18f461a ro quiet noapic splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb77fb5b7 <ply_event_loop_process_pending_events+455>: test %ecx,0x4(%esi)
 PC (0xb77fb5b7) 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-01-27 (1 days ago)
UserGroups:

dmi.bios.date: 09/27/2006
dmi.bios.vendor: Phoenix
dmi.bios.version: 2004 Q1
dmi.board.name: VN800
dmi.board.vendor: VIA
dmi.board.version: VT6297A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr2004Q1:bd09/27/2006:svnVIA:pnVN800:pvrVT6297A:rvnVIA:rnVN800:rvrVT6297A:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VN800
dmi.product.version: VT6297A
dmi.sys.vendor: VIA

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  Edit
Everyone can see this information.

Other bug subscribers