plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Thomas H St.Clair]

just normal logon.

lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

every login-
expected- no error
experienced- crash

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: plymouth 0.8.8-0ubuntu15
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Wed Mar 5 07:40:12 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-03-05 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140115)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=053a682e-4827-4016-b439-e20f37436cba ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=053a682e-4827-4016-b439-e20f37436cba ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7ff67f3ae430 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7ff67f3ae430) ok
 source "$0x1" ok
 destination "(%rdi)" (0x43800000780) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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.2
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: 08/22/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F14
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-UD5H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd08/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Apport retracing service (apport)]

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 #1223714, 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.

[Launchpad Janitor (janitor)]

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

[Dora (tiggernut24)]

Don't just tell us how to fix it or anything, Your Royal Highnesses!

And the fact that multiple users have this bug hardly makes me feel better!

Come DOWN off your high horse, and TELL US HOW TO FIX IT.

Or fix it yourselves.

Thank you! For nothing!

[Daniel (cdtenzi)]

fix it yourself: sudo chown -R user:user /lib/plymouth

[Steve Langasek (vorlon)]

On Thu, Oct 29, 2015 at 04:02:10PM -0000, Daniel wrote:
> *** This bug is a duplicate of bug 927636 ***
> https://bugs.launchpad.net/bugs/927636

> fix it yourself: sudo chown -R user:user /lib/plymouth

That is absolutely not an appropriate fix for this bug.