plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #955651 reported by Carlos García
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Similar to other bugs, bu this appeared after fresh install and updates in 12.04, not 10.04.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CurrentDmesg:
 [ 35.032169] wlan0: no IPv6 routers present
 [ 36.589038] init: plymouth-stop pre-start process (1323) terminated with status 1
Date: Wed Mar 14 18:57:22 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=f53da738-6d83-4ef9-90cd-1a009c72e48e ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=f53da738-6d83-4ef9-90cd-1a009c72e48e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f015a06c504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7f015a06c504) 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: 09/08/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 02QN.MI99.20110908.SKK
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 305V4A/305V4A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 02QN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr02QN.MI99.20110908.SKK:bd09/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305V4A/305V5A:pvr02QN:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305V4A/305V4A:rvr02QN:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 305V4A/305V5A
dmi.product.version: 02QN
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Carlos García (carlos-gs12) wrote :
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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-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.