plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #961607 reported by Emilio Vega Roa on 2012-03-21
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

first restart after updates

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 21 17:01:14 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
MachineType: Acer AOD255E
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic root=UUID=c09eed32-0c50-425b-bc95-39f5b8fbac24 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-19-generic root=UUID=c09eed32-0c50-425b-bc95-39f5b8fbac24 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f31764ae504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7f31764ae504) 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: Upgraded to precise on 2012-03-12 (9 days ago)
UserGroups:

dmi.bios.date: 04/22/2011
dmi.bios.vendor: Acer
dmi.bios.version: V3.16(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT_E
dmi.board.vendor: Acer
dmi.board.version: V3.16(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.16(DDR3)
dmi.modalias: dmi:bvnAcer:bvrV3.16(DDR3):bd04/22/2011:svnAcer:pnAOD255E:pvrV3.16(DDR3):rvnAcer:rnJE02_PT_E:rvrV3.16(DDR3):cvnAcer:ct10:cvrV3.16(DDR3):
dmi.product.name: AOD255E
dmi.product.version: V3.16(DDR3)
dmi.sys.vendor: Acer

Emilio Vega Roa (tehxnik) 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