plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #559930 reported by Andrew Pam
252
This bug affects 60 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: plymouth

plymouthd does not exit when system is booted. Ubuntu logo and four dots remain on screen, cannot change to text mode virtual terminals or X windows. Can log in via SSH but can not kill plymouthd even with kill -KILL. ACPI power button also works.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 19:58:08 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
 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: IBM 288175M
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: root=UUID=e97866c4-7397-4fc5-9047-13137af8d817 ro quiet
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
SegvAnalysis:
 Segfault happened at: 0x857ae8 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0x00857ae8) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_trigger_add_handler () from /lib/libply.so.2
 ?? ()
 ?? ()
 ply_event_loop_process_pending_events ()
 ply_event_loop_run () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UserGroups:

dmi.bios.date: 01/14/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1XET47WW (1.06 )
dmi.board.name: 288175M
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1XET47WW(1.06):bd01/14/2005:svnIBM:pn288175M:pvrThinkPadG41:rvnIBM:rn288175M:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 288175M
dmi.product.version: ThinkPad G41
dmi.sys.vendor: IBM

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

StacktraceTop:
 ply_trigger_add_handler (trigger=0x0,
 on_deactivate (state=0xbfa257a8,
 ply_boot_connection_on_request (connection=0x8d74c90)
 ply_event_loop_process_pending_events (
 ply_event_loop_run (loop=0x8d6f0a8) at ply-event-loop.c:1312

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
Daniel Hahler (blueyed)
visibility: private → public
Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
cecilpierce (piercececil-deactivatedaccount) wrote :

First time I seen this, its OLD.

Revision history for this message
Domen Vrankar (domen-vrankar) wrote :

This is occuring to me since I upgraded to 12.10 beta 1. I thought that it was a problem with the graphics drivers related to having nvidia optimus.

How to log in:
When I notice that the mouse button gets changed to an arrow and the login screen isn't shown for one to two seconds (after this time the mouse and keyboard stop responding so this has to be done before that happens) I press alt + ctrl +f1 and log in with my user.
Then I restart the gdm with sudo /etc/init.d/gdm restart and the login screen shows up so you can log in normally.

I'm using gnome-shell and gdm.

Revision history for this message
lunab1 (emanuela-davide) wrote :

I logged in and there was the error, I did nothing special but loggin in. The OS is now working properly.
I'm using gnome-shell

description: updated
Revision history for this message
dino99 (9d9) wrote :

This version is now outdated and no more supported

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