plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #965924 reported by Philip Khor on 2012-03-27
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Crashed at startup

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Tue Mar 27 13:13:29 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: Hewlett-Packard Compaq Presario CQ40 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=13f5f112-4c22-4e0e-9c64-3b0d748e5b40 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=13f5f112-4c22-4e0e-9c64-3b0d748e5b40 ro quiet splash vt.handoff=7
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-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/29/2010
dmi.bios.vendor: Insyde
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3607
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 99.C4
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnInsyde:bvrF.67:bd11/29/2010:svnHewlett-Packard:pnCompaqPresarioCQ40NotebookPC:pvrF.67:rvnHewlett-Packard:rn3607:rvr99.C4:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Compaq Presario CQ40 Notebook PC
dmi.product.version: F.67
dmi.sys.vendor: Hewlett-Packard

Philip Khor (philip10khor) wrote :

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-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers