plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Bug Description

i915 errors in kernel log

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Thu Oct 15 00:31:52 2015
DefaultPlymouth: /lib/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: Hewlett-Packard 300-016d
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=df51fde7-e62f-4a58-ad79-37ef6ab816a8 ro splash quiet vt.handoff=7
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-16-generic.efi.signed root=UUID=df51fde7-e62f-4a58-ad79-37ef6ab816a8 ro splash quiet vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f65292ae600 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f65292ae600) 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-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-06 (8 days ago)
UserGroups:

dmi.bios.date: 12/15/2014
dmi.bios.vendor: AMI
dmi.bios.version: 80.03
dmi.board.asset.tag: 3CR51306RT
dmi.board.name: 2B38
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.02
dmi.chassis.asset.tag: 3CR51306RT
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr80.03:bd12/15/2014:svnHewlett-Packard:pn300-016d:pvr:rvnHewlett-Packard:rn2B38:rvr1.02:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 300-016d
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Thomas Christensen (christensenthomas) 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 #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.

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.