plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashes during system boot
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu8 [modified: bin/plymouth bin/plymouth-
ProcVersionSign
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Fri Oct 11 20:40:20 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-10-11 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130907)
MachineType: HP Pavilion 061 RJ073AA-ABZ m7695.it
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f2c2351e430 <script_
PC (0x7f2c2351e430) ok
source "$0x1" ok
destination "(%rdi)" (0x404040104000000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/21/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.17
dmi.board.name: Basswood
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.05
dmi.chassis.type: 3
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: RJ073AA-ABZ m7695.it
dmi.product.
dmi.sys.vendor: HP Pavilion 061
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 #927636, 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.