plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1279348 reported by Bernard Puc
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

booting 14.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu14
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
Date: Wed Feb 12 08:39:24 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-02-07 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140207)
MachineType: Dell Inc. Precision M4700
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=e4745aa7-937e-4cd5-a135-f95ff29758bb ro quiet splash
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=e4745aa7-937e-4cd5-a135-f95ff29758bb ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7ffc6a02a430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7ffc6a02a430) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 script_obj_deref_direct () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_update_status () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/20/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 082H3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/20/2013:svnDellInc.:pnPrecisionM4700:pvr01:rvnDellInc.:rn082H3V:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4700
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Bernard Puc (bernpuc) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.