plymouthd crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I just received this dialog.
~$lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
~$ apt-cache policy plymouth
plymouth:
已安装: 0.8.2-2ubuntu28
候选软件包:
版本列表:
*** 0.8.2-2ubuntu28 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.2.0-17-generic i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Mar 1 21:40:22 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
MachineType: LENOVO Brazos
ProcCmdLine: root=UUID=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: root=UUID=
SegvAnalysis:
Segfault happened at: 0x80a350: cmp 0xc(%eax),%esi
PC (0x0080a350) ok
source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
?? () from /lib/i386-
?? ()
?? ()
?? ()
__libc_start_main () from /lib/i386-
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to precise on 2012-02-20 (10 days ago)
UserGroups:
dmi.bios.date: 04/15/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 4BCN20WW
dmi.board.
dmi.board.name: Inagua
dmi.board.vendor: LENOVO
dmi.board.version: 109-B78210-00A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: Brazos
dmi.product.
dmi.sys.vendor: LENOVO
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 #938971, 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.