plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1205587 reported by Rigved Rakshit
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

plymouth:
  Installed: 0.8.8-0ubuntu7
  Candidate: 0.8.8-0ubuntu7
  Version table:
 *** 0.8.8-0ubuntu7 0
        500 http://in.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Jul 27 11:35:13 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2012-09-09 (320 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: L3000 Y300 Y300
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=cee889aa-734c-48c2-b4f7-8641ab7af377 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=cee889aa-734c-48c2-b4f7-8641ab7af377 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb7764618 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb7764618) 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/i386-linux-gnu/libply.so.2
 ?? ()
 ?? ()
 ply_event_loop_process_pending_events () from /lib/i386-linux-gnu/libply.so.2
 ply_event_loop_run () from /lib/i386-linux-gnu/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 saucy on 2013-05-15 (73 days ago)
UserGroups:

dmi.bios.date: 11/06/06
dmi.bios.vendor: Lenovo
dmi.bios.version: Q3B11W
dmi.board.name: Y300
dmi.board.vendor: L3000 Y300
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLenovo:bvrQ3B11W:bd11/06/06:svnL3000Y300:pnY300:pvrRev1.0:rvnL3000Y300:rnY300:rvrNotApplicable:cvnLenovo:ct10:cvrN/A:
dmi.product.name: Y300
dmi.product.version: Rev 1.0
dmi.sys.vendor: L3000 Y300

Revision history for this message
Rigved Rakshit (rigved) 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
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.