plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1501799 reported by siucdude
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This looks like old bugs, but on Ubuntu 15.10,
Thanks
TJ

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-13.15-generic 4.2.1
Uname: Linux 4.2.0-13-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 1 09:48:48 2015
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2011-04-03 (1641 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
MachineType: LENOVO 20DM000VUS
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-13-generic root=UUID=02993959-dfdc-418a-91d6-600a20b78305 ro quiet splash
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-13-generic root=UUID=02993959-dfdc-418a-91d6-600a20b78305 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7f096a3e5600 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f096a3e5600) ok
 source "$0x1" ok
 destination "(%rdi)" (0x00000001) 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_boot_progress () from /lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to wily on 2014-10-24 (342 days ago)
UserGroups:

dmi.bios.date: 03/26/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JGET25WW (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20DM000VUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrJGET25WW(1.11):bd03/26/2015:svnLENOVO:pn20DM000VUS:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM000VUS:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20DM000VUS
dmi.product.version: ThinkPad S3 Yoga 14
dmi.sys.vendor: LENOVO

Revision history for this message
siucdude (siucdude) wrote :
information type: Private → Public
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 #1417523, 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.

tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
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.