plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1552370 reported by Carlos Suárez
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crash on reboot after update 2016-03-02 with new kernel 4.4.0.9

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: plymouth 0.9.2-3ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Wed Mar 2 19:26:27 2016
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2016-02-21 (10 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160220)
MachineType: Acer Aspire X3950
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=a9ea69ac-cba3-4032-a9c7-1f977919a1a0 ro quiet splash
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=a9ea69ac-cba3-4032-a9c7-1f977919a1a0 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7fbc3ad54660 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7fbc3ad54660) 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 /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_boot_progress () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.4
TextPlymouth: /usr/share/plymouth/themes/text/text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/13/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A2
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Aspire X3950
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A2:bd04/13/2010:svnAcer:pnAspireX3950:pvr:rvnAcer:rnAspireX3950:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire X3950
dmi.sys.vendor: Acer

Revision history for this message
Carlos Suárez (bitseater) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 script_obj_deref_direct () from /tmp/apport_sandbox_CYG7hz/usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_obj_as_custom () from /tmp/apport_sandbox_CYG7hz/usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_execute_object () from /tmp/apport_sandbox_CYG7hz/usr/lib/x86_64-linux-gnu/plymouth/script.so
 script_lib_plymouth_on_boot_progress () from /tmp/apport_sandbox_CYG7hz/usr/lib/x86_64-linux-gnu/plymouth/script.so
 ply_boot_splash_update_progress () from /tmp/apport_sandbox_CYG7hz/lib/x86_64-linux-gnu/libply-splash-core.so.4

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: yakkety
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
Andrea Azzarone (azzar1)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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