plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Came after the update.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDmesg:
[ 17.674243] atl1c 0000:02:00.0: >atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
[ 20.373007] init: plymouth main process (267) killed by SEGV signal
[ 20.564940] init: plymouth-stop pre-start process (1283) terminated with status 1
Date: Fri Oct 5 16:46:20 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
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: 0x7f1f64a741c0 <script_
PC (0x7f1f64a741c0) 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: 06/09/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: G41M-Combo
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: G41M-Combo
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.