gnomad2 crashed with SIGSEGV in g_thread_create_proxy()

Bug #578484 reported by selbst on 2010-05-10
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnomad2 (Ubuntu)
Medium
Unassigned
Lucid
Undecided
Unassigned

Bug Description

Binary package hint: gnomad2

Description: Ubuntu 10.04 LTS
Release: 10.04

gnomad2:
  Installiert: 2.9.4-1
  Kandidat: 2.9.4-1
  Versions-Tabelle:
 *** 2.9.4-1 0

When I start gnomad2 with my Creative ZEN Vision:M on USB port, it closes after the popped up 'receiving window' has done loading data from the ZEN player.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnomad2 2.9.4-1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon May 10 22:31:48 2010
ExecutablePath: /usr/bin/gnomad2
ProcCmdline: gnomad2
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x412b0b: mov 0x70(%rbp),%edx
 PC (0x00412b0b) ok
 source "0x70(%rbp)" (0x00000071) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnomad2
StacktraceTop:
 ?? ()
 g_thread_create_proxy (data=0x7fec6c009580)
 start_thread (arg=<value optimized out>)
 clone ()
 ?? ()
Title: gnomad2 crashed with SIGSEGV in g_thread_create_proxy()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

selbst (ronald-schulze1) wrote :

StacktraceTop:
 scan_thread (thread_args=<value optimized out>) at jukebox.c:1598
 g_thread_create_proxy (data=0x7fec6c009580)
 start_thread () from /lib/libpthread.so.0
 clone ()
 ?? ()

Changed in gnomad2 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
selbst (ronald-schulze1) on 2010-05-17
visibility: private → public
Alessio Treglia (quadrispro) wrote :

No longer available in Maverick.
Closing.

Changed in gnomad2 (Ubuntu):
status: New → Invalid
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in gnomad2 (Ubuntu Lucid):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers