plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
N/A
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Fri Oct 5 11:32:27 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: System manufacturer System Product Name
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: 0x7f7aec9da1c0 <script_
PC (0x7f7aec9da1c0) 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: Upgraded to quantal on 2012-10-02 (5 days ago)
UserGroups:
dmi.bios.date: 04/06/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0221
dmi.board.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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 #1032932, 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.