plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1582497 reported by martyfelker on 2016-05-17
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Ubuntu 16.10 (Yakkey Yak) Initial Boot to GUI

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: plymouth 0.9.2-3ubuntu15
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
Date: Mon May 16 23:50:55 2016
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2016-05-17 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160516)
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=1ae5e651-e3db-4f0b-b5f8-e2b5c75bdbea ro quiet splash 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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=1ae5e651-e3db-4f0b-b5f8-e2b5c75bdbea ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f7b4b592630 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f7b4b592630) ok
 source "$0x1" ok
 destination "(%rdi)" (0x2f30303a30303030) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/30/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

martyfelker (martyfelker-gmail) wrote :
martyfelker (martyfelker-gmail) wrote :

Ubuntu 16.10 (Yakkety Yak)

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 #1552370, 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
Launchpad Janitor (janitor) wrote :

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

Changed in plymouth (Ubuntu):
status: New → Confirmed
Mathew Garland (matg) on 2016-11-14
description: updated
Mathew Garland (matg) wrote :

Can not find bug#1552370, removed duplicate status.

Also affecting Xenial 16.04.1 LTS

Richard Trinkner (trinkner) wrote :

Still affects me on 16.04 LTS, running Gnome desktop. Kernel 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 16:07:46 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers