plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #864289 reported by Önder on 2011-10-01
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

No idea about this package but I've faced with it when opening the CCSM.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 1 23:13:18 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
MachineType: Packard Bell DOT SE
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=5f0935ee-2ef3-44eb-9353-3e1a9d879d7b 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.0.0-12-generic root=UUID=5f0935ee-2ef3-44eb-9353-3e1a9d879d7b ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fb2d6a2d504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7fb2d6a2d504) ok
 source "%r12d" ok
 destination "0x8(%r13)" (0x00000008) 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/x86_64-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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/17/2010
dmi.bios.vendor: Packard Bell
dmi.bios.version: V3.10(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.10(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V3.10(DDR3)
dmi.modalias: dmi:bvnPackardBell:bvrV3.10(DDR3):bd11/17/2010:svnPackardBell:pnDOTSE:pvrV3.10(DDR3):rvnAcer:rnSJE02_PT:rvrV3.10(DDR3):cvnPackardBell:ct10:cvrV3.10(DDR3):
dmi.product.name: DOT SE
dmi.product.version: V3.10(DDR3)
dmi.sys.vendor: Packard Bell

Önder (onder.bakirtas) wrote :

Thank you for taking the time to report this crash and helping to make Ubuntu 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