Exiting from system - ubuntu logo stays on screen - plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1096038 reported by Wojciech Ziniewicz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

My system was being upgraded gradually from 11.04 till 12.10 . Everything's fine except for ubuntu logo staying during reboot with "sudo reboot" typed into console.

--
Description: Ubuntu 12.10
Release: 12.10
--
[wojtek@wojtek-ThinkPad-T60 ~]$ apt-cache policy plymouth
plymouth:
  Installed: 0.8.4-0ubuntu3
  Candidate: 0.8.4-0ubuntu3
  Version table:
 *** 0.8.4-0ubuntu3 0
        500 http://pl.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
        100 /var/lib/dpkg/status
--

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Fri Jan 4 13:23:21 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2012-07-24 (163 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: LENOVO 2007FRG
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=19d25b37-7fe7-46f3-a36f-38dbc43f94d3 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=19d25b37-7fe7-46f3-a36f-38dbc43f94d3 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb7782b28 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb7782b28) 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 () from /lib/libply.so.2
 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()
UpgradeStatus: Upgraded to quantal on 2012-09-27 (99 days ago)
UserGroups:

dmi.bios.date: 09/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE3WW (2.23 )
dmi.board.name: 2007FRG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007FRG:pvrThinkPadT60:rvnLENOVO:rn2007FRG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2007FRG
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

Revision history for this message
Wojciech Ziniewicz (wojciech-ziniewicz) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #750405, 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-i386-retrace
Revision history for this message
Wojciech Ziniewicz (wojciech-ziniewicz) wrote :

Hi,
of course this is a duplicate - I was wondering if this information helps somehow to fix the plymouth.
This is probably very complicated problem but will it be OK if I submit the patch for this bug ?

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.