plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #554851 reported by sb92075
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

 lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04
 apt-cache policy plymouth
plymouth:
  Installed: 0.8.1-4
  Candidate: 0.8.1-4
  Version table:
 *** 0.8.1-4 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
CurrentDmesg: [ 27.780631] eth0: no IPv6 routers present
Date: Sat Apr 3 15:01:03 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: TOSHIBA Satellite M305D
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=3976dfc5-91f8-45ae-ba15-8ffc19a79170 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
SegvAnalysis:
 Segfault happened at: 0x7ff83350509c <ply_event_loop_process_pending_events+508>: test %r12d,0x8(%r13)
 PC (0x7ff83350509c) ok
 source "%r12d" ok
 destination "0x8(%r13)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_event_loop_process_pending_events ()
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UserGroups:

dmi.bios.date: 10/01/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V2.20
dmi.board.name: Satellite M305D
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV2.20:bd10/01/2008:svnTOSHIBA:pnSatelliteM305D:pvrPSMDYU-00C005:rvnTOSHIBA:rnSatelliteM305D:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:
dmi.product.name: Satellite M305D
dmi.product.version: PSMDYU-00C005
dmi.sys.vendor: TOSHIBA

Revision history for this message
sb92075 (sol-beach) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #553745, 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-amd64-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.