plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

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

Bug Description

Occured while minimizing Chromium.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic i686
ApportVersion: 2.8-0ubuntu2
Architecture: i386
Date: Fri Jan 25 07:37:53 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-01-15 (10 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: Packard Bell EasyNote TJ65
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=ae73c08e-8bb9-49d7-8ac3-6eaa0ea1a175 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcCwd: /
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=ae73c08e-8bb9-49d7-8ac3-6eaa0ea1a175 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb779eac8 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb779eac8) 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 raring on 2013-01-24 (1 days ago)
UserGroups:

dmi.bios.date: 12/24/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.31
dmi.board.name: SJV50MV
dmi.board.vendor: Packard Bell
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.31:bd12/24/2009:svnPackardBell:pnEasyNoteTJ65:pvr0100:rvnPackardBell:rnSJV50MV:rvrRev:cvnPackardBell:ct10:cvrN/A:
dmi.product.name: EasyNote TJ65
dmi.product.version: 0100
dmi.sys.vendor: Packard Bell

Revision history for this message
Dominik (dominik-schlack) 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.