ubuntu plymouth crashed on system startup
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
ProcVersionSign
Uname: Linux 3.5.0-17-generic i686
NonfreeKernelMo
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(134953242
Date: Thu Oct 4 00:30:04 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha i386(20120912)
MachineType: TOSHIBA Satellite C660
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb7715b28 <ply_trigger_
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_
?? ()
?? ()
ply_event_
ply_event_loop_run () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_trigger_
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.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite C660
dmi.product.
dmi.sys.vendor: TOSHIBA
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.