plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1043365 reported by Leen2911
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

by testing ubuntu 12.10 after update's

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu3
Architecture: i386
Date: Wed Aug 29 10:26:44 2012
DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120825)
Lsusb:
 Bus 002 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=31f895b9-04fd-43bb-8cc7-a459f5a7e111 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=31f895b9-04fd-43bb-8cc7-a459f5a7e111 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb77a1b28 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb77a1b28) 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/xubuntu-text/xubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/19/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: K7VT4A+
dmi.board.version: 1.0x
dmi.chassis.asset.tag: 00000000
dmi.chassis.type: 3
dmi.chassis.version: X.XX
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/19/2004:svn:pnK7VT4A+:pvr1.0x:rvn:rnK7VT4A+:rvr1.0x:cvn:ct3:cvrX.XX:
dmi.product.name: K7VT4A+
dmi.product.version: 1.0x

Revision history for this message
Leen2911 (leen-van-den-adel) 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.

visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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