plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

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

Bug Description

plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
Uname: Linux 3.9.0-6-generic i686
ApportVersion: 2.10.2-0ubuntu2
Architecture: i386
Date: Sat Jun 22 12:37:41 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-06-18 (3 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130618)
MachineType: ASUSTeK COMPUTER INC. 1025C
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=bd7ff9d9-3acb-4cfb-a5f7-b34b7671c6e1 ro recovery nomodeset
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 psbfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=bd7ff9d9-3acb-4cfb-a5f7-b34b7671c6e1 ro recovery nomodeset
SegvAnalysis:
 Segfault happened at: 0xb7774618 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb7774618) 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1025C.0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 1025C
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1025C.0801:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
dmi.product.name: 1025C
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
rolmops (dr150259) 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.