plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the bugs that were shown were of 12.04LTS, hence listing this as new. This been troubling me for more than amonth now. I'm sure there will be duplicates too.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu8
ProcVersionSign
Uname: Linux 3.11.0-
NonfreeKernelMo
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 8 16:31:31 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-08-24 (45 days ago)
InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Alpha amd64 (20130811)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 305E4Z/
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f25a2f4b430 <script_
PC (0x7f25a2f4b430) ok
source "$0x1" ok
destination "(%rdi)" (0x726f20746579
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? () from /lib/x86_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 01TK.ME30.
dmi.board.
dmi.board.name: 305E4Z/305E4Z
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 01TK
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 305E4Z/
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS 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.