gnomad2 crashed with signal 7 in start_thread()
Brought to you by:
snirkel
Menu
▾
▴
#253 gnomad2 crashed with signal 7 in start_thread()
This bug was originally reported to Launchpad.
For more information, please see https://bugs.launchpad.net/ubuntu/+source/gnomad2/+bug/509033
I'm trying to connect my Creative Zen V 4GB to my Ubuntu system to transfer music. This has been very hit and miss over the years. MTP support for this device seems very bad. Recently no program is able to transfer music correctly to the device. This time gnomad2 just crashes.
Attached is the crash detection report. I'm running Lucid alpha 2. No other problems with USB devices.
gnomad2:
Installed: 2.9.4-1
Candidate: 2.9.4-1
Version table:
*** 2.9.4-1 0
500 http://gb.archive.ubuntu.com lucid/universe Packages
100 /var/lib/dpkg/status
Steps to reproduce:
1) Start gnomad2
2) Connect a device into the USB port
3) Scan the contents of the device
Expected result:
Contents appears in gnomad2 after scan is complete
Actual result:
gnomad2 crashes
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 18 07:42:47 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnomad2
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
Package: gnomad2 2.9.4-1
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: gnomad2
ProcEnviron:
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 7
SourcePackage: gnomad2
StacktraceTop:
?? ()
?? () from /lib/libglib-2.0.so.0
start_thread () from /lib/libpthread.so.0
clone () from /lib/libc.so.6
?? ()
Tags: lucid
Title: gnomad2 crashed with signal 7 in start_thread()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups:
meteorological united criticized biological dimming place climatic fuels [url=http://www.maccompanion.com]warmest main[/url] http://www.aph.gov.au
I recently made a thorough overhaul of Gnomad2, removing many bugs, as a result I think it has been re-adopted to Debian (it was staged for removal). Can you please try the 2.9.6 version and see if the problem persists?