plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1274859 reported by Jaime Pérez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

After last upgrade.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
Date: Fri Jan 31 10:10:41 2014
DefaultPlymouth: /lib/plymouth/themes/edubuntu-logo/edubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-01-17 (13 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: MSI MS-7640
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=c33c2abb-8df7-49fa-8190-5f0d00f7c47b ro quiet splash radeon.audio=1 vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 simple
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=c33c2abb-8df7-49fa-8190-5f0d00f7c47b ro quiet splash radeon.audio=1 vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fcd88bea430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fcd88bea430) ok
 source "$0x1" ok
 destination "(%rdi)" (0x726f207465792079) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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_display_message () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/plymouth/script.so
TextPlymouth: /lib/plymouth/themes/edubuntu-text/edubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to trusty on 2014-01-27 (3 days ago)
UserGroups:

dmi.bios.date: 10/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V19.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-GD65 (MS-7640)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 3.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV19.9:bd10/08/2012:svnMSI:pnMS-7640:pvr3.0:rvnMSI:rn990FXA-GD65(MS-7640):rvr3.0:cvnMSI:ct3:cvr3.0:
dmi.product.name: MS-7640
dmi.product.version: 3.0
dmi.sys.vendor: MSI

Revision history for this message
Jaime Pérez (jaime-91) 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 #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.

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.