plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu8
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory
Date: Sat Oct 5 13:37:01 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-09-15 (22 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130915)
MachineType: MSI MS-7640
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic.efi.signed root=UUID=bbcd0d22-ba5e-48e9-8583-2062870c5211 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic.efi.signed root=UUID=bbcd0d22-ba5e-48e9-8583-2062870c5211 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fba1f5d8430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fba1f5d8430) 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: 07/12/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V13.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-GD80 (MS-7640)
dmi.board.vendor: MSI
dmi.board.version: 2.2
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.2
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV13.4:bd07/12/2013:svnMSI:pnMS-7640:pvr2.2:rvnMSI:rn990FXA-GD80(MS-7640):rvr2.2:cvnMSI:ct3:cvr2.2:
dmi.product.name: MS-7640
dmi.product.version: 2.2
dmi.sys.vendor: MSI

Revision history for this message
lulo (lulojs11) wrote :
Changed in plymouth (Ubuntu):
assignee: nobody → lulo (lulojs11)
assignee: lulo (lulojs11) → nobody
Revision history for this message
lulo (lulojs11) wrote :

I'am remove /var/log/{dmesg*,kern*,syslog*} - using /etc/rc.local:

rm -f /var/log/kern*
rm -f /var/log/dmesg*
rm -f /var/log/syslog*

I need this fix - this files its big values to 8-10 restart (many GB).
Problem: https://answers.launchpad.net/ubuntu/+question/234598

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.