plymouthd crashed with SIGSEGV in ply_list_remove_node()

Bug #745744 reported by Eliah Kagan
430
This bug affects 87 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: plymouth

I installed from today's Natty i386 daily-live CD (dated 20110329, md5sum 76b056698985ee95ab4838d5157e5a70), updated the system, rebooted a couple of times, and was then informed of this error. The system has plymouth/libplymouth2 0.8.2-2ubuntu21. This bug loosely resembles bug 542191 and bug 554510, but in those bugs the crash occurred in different functions (ply_list_remove_all_nodes() in bug 542191, ply_list_get_first_node() in bug 554510, and ply_list_remove_node() in this bug).

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Wed Mar 30 09:54:20 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta 1 i386 (20110329.1)
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: VMware, Inc. VMware Virtual Platform
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=c31eb5a5-e457-4e6b-b99e-7f8edb554edc ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xf8e13f <ply_list_remove_node+47>: mov %ecx,0x8(%edx)
 PC (0x00f8e13f) ok
 source "%ecx" ok
 destination "0x8(%edx)" (0x00000019) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_list_remove_node () from /lib/libply.so.2
 ply_list_remove_all_nodes () from /lib/libply.so.2
 ply_list_free () from /lib/libply.so.2
 ?? () from /lib/libply.so.2
 ply_event_loop_process_pending_events () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_list_remove_node()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/31/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/31/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ply_list_unlink_node (list=0x9860ad8, node=0x9860b38) at ply-list.c:211
 ply_list_remove_node (list=0x9860ad8, node=0x9860b38) at ply-list.c:233
 ply_list_remove_all_nodes (list=0x9860ad8) at ply-list.c:250
 ply_list_free (list=0x9860ad8) at ply-list.c:64
 ply_event_source_free (source=0x9860ac0) at ply-event-loop.c:354

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Ryan Kitty (gothickitty93) wrote :

just experienced this with oneiric

tags: added: oneiric
Revision history for this message
Carlos Donizete Froes (coringao) wrote :
Revision history for this message
Kevin S (ks20xx) wrote :

Confirmed on 11.10 amd64 arch.

Steve Langasek (vorlon)
Changed in plymouth (Ubuntu):
importance: Medium → High
Revision history for this message
Steve Langasek (vorlon) wrote :

We believe this has been resolved with the application of a workaround for bug #553745. If you continue to see this behavior in Ubuntu 12.04 LTS, please reopen this report and provide details.

Changed in plymouth (Ubuntu):
status: Confirmed → Fix Released
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.