plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #553072 reported by Bordi
136
This bug affects 31 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: plymouth

#lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

#uname -a
Linux ubuntu 2.6.32-18-generic #27-Ubuntu SMP Fri Mar 26 21:13:44 UTC 2010 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-2
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
Architecture: amd64
CurrentDmesg:
 [ 21.330055] eth0: no IPv6 routers present
 [ 23.091568] ISO 9660 Extensions: Microsoft Joliet Level 3
 [ 23.247585] ISO 9660 Extensions: RRIP_1991A
Date: Mon Mar 29 14:28:00 2010
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-18-generic root=UUID=72211b64-851f-43cb-bd50-9e01b6b10f2d ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VGA16 VGA
SegvAnalysis:
 Segfault happened at: 0x7f60f5a1f500 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f60f5a1f500) 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 ()
 script_obj_as_custom () from /lib/plymouth/script.so
 script_execute_object ()
 script_lib_plymouth_on_boot_progress ()
 ?? () from /lib/libply-splash-core.so.2
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UserGroups:

dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Bordi (borderlinedancer) wrote :
visibility: private → public
Revision history for this message
Steve Langasek (vorlon) wrote :

What theme are you using (what does /etc/alternatives/default.plymouth point to)?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Given the crash, it can only be one of our themes ;-)

Changed in plymouth (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Steve Langasek (vorlon) wrote :

There are several forks of the ubuntu-logo theme is the archive now for Ubuntu flavors, which could have relevant differences.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 script_obj_deref_direct ()
 script_obj_as_custom () from /lib/plymouth/script.so
 script_execute_object ()
 script_lib_plymouth_on_boot_progress ()
 ?? () from /lib/libply-splash-core.so.2

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: removed: need-amd64-retrace
Revision history for this message
michael brenden (mike-brenden) wrote :

I had similar problem.

I had removed "quiet splash" from the kernel parameters. Re-added those two using grub and system booted into graphic splash. An error was reported in that graphic splash, and required S to skip or M to fix manually. There were three errors, actually, all for missing disks in the /etc/fstab.

Revision history for this message
michael brenden (mike-brenden) wrote :
Revision history for this message
michael brenden (mike-brenden) wrote :
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.