plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Apport brought this up. waste of time really as you will not work on this dog anyway.
Easy fix anyway, allow people to remove plymouth. Would be nice to be able to boot in less than 3 to 20 minutes.
It was less than 4 minutes but still, come on boys, admit that it is badly flawed.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 2 21:07:06 2011
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.3)
MachineType: Dell Inc. Dell XPS420
ProcCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda11 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda11 ro quiet splash
SegvAnalysis:
Segfault happened at: 0x7f2ce58d5ea0 <script_
PC (0x7f2ce58d5ea0) ok
source "$0x1" ok
destination "(%rdi)" (0x726f20746579
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? () from /lib/plymouth/
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 03/27/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TP406
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell XPS420
dmi.sys.vendor: Dell Inc.
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #733453, 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.