ubuntu plymouth crashed on system startup

Bug #1062857 reported by abdouett
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When the system boots, a message appears indicating a bug caused by a malfunction of plymouth

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CurrentDmesg:
 [ 24.890754] init: anacron main process (1012) killed by TERM signal
 [ 3362.100480] [Firmware Bug]: battery: (dis)charge rate invalid.
 [ 6944.335687] audit_printk_skb: 39 callbacks suppressed
 [ 6944.335692] type=1701 audit(1349532428.769:25): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=10837 comm="chrome" reason="seccomp" sig=0 syscall=20 compat=0 ip=0xb3736424 code=0x50000
Date: Thu Oct 4 00:30:04 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha i386(20120912)
MachineType: TOSHIBA Satellite C660
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=fb571a8d-9008-4a29-94a5-629d8122336c 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.5.0-17-generic root=UUID=fb571a8d-9008-4a29-94a5-629d8122336c ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb7715b28 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb7715b28) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_trigger_add_handler () from /lib/libply.so.2
 ?? ()
 ?? ()
 ply_event_loop_process_pending_events () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/16/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.30
dmi.board.name: PWWAM
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd02/16/2011:svnTOSHIBA:pnSatelliteC660:pvrPSC0NE-00100CG4:rvnTOSHIBA:rnPWWAM:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite C660
dmi.product.version: PSC0NE-00100CG4
dmi.sys.vendor: TOSHIBA

Revision history for this message
abdouett (test-win8) 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 #750405, 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
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
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.