GNOME Bugzilla – Bug 627349
Crashes while transfering music using an MTP device
Last modified: 2010-08-24 16:00:00 UTC
Originally reported at: https://bugs.launchpad.net/bugs/614990 Binary package hint: banshee hello, I think I have found a bug with banshee. I'm using a MP3 player with the MTP (samsung YP-T10) and when I transfert music with banshee, it crashes at random (it can be at the first music or another) here is what the console report : [Info 00:11:17.676] Running Banshee 1.6.1: [Ubuntu 10.04 LTS (linux-gnu, i486) @ 2010-06-18 09:51:55 UTC] [Info 00:11:21.929] All services are started 3,565602 [Info 00:11:25.550] nereid Client Started Device 0 (VID=04e8 and PID=508a) is a Samsung YP-T10. PTP_ERROR_IO: Trying again after re-initializing USB interface MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered MTP extended association type 0x00000001 encountered Stacktrace: Native stacktrace: banshee-1() [0x80ca6e4] banshee-1() [0x80f6893] [0x714410] Debug info from gdb: [Thread debugging using libthread_db enabled] [New Thread 0x3877b70 (LWP 4514)] [New Thread 0xa141b70 (LWP 4511)] [New Thread 0x3fb9b70 (LWP 4510)] [New Thread 0xa19cb70 (LWP 4506)] [New Thread 0x3eb8b70 (LWP 4504)] [New Thread 0x3cdab70 (LWP 4503)] [New Thread 0x3a3cb70 (LWP 4502)] [New Thread 0xb62b9b70 (LWP 4500)] [New Thread 0x2fe1b70 (LWP 4499)] [New Thread 0x8e4ab70 (LWP 4497)] [New Thread 0x8972b70 (LWP 4496)] [New Thread 0x6deb70 (LWP 4495)] 0x08110da0 in mono_object_new_specific () 13 Thread 0x6deb70 (LWP 4495) 0x00714422 in __kernel_vsyscall () 12 Thread 0x8972b70 (LWP 4496) 0x00714422 in __kernel_vsyscall () 11 Thread 0x8e4ab70 (LWP 4497) 0x00714422 in __kernel_vsyscall () 10 Thread 0x2fe1b70 (LWP 4499) 0x00714422 in __kernel_vsyscall () 9 Thread 0xb62b9b70 (LWP 4500) 0x00714422 in __kernel_vsyscall () 8 Thread 0x3a3cb70 (LWP 4502) 0x00714422 in __kernel_vsyscall () 7 Thread 0x3cdab70 (LWP 4503) 0x00714422 in __kernel_vsyscall () 6 Thread 0x3eb8b70 (LWP 4504) 0x00714422 in __kernel_vsyscall () 5 Thread 0xa19cb70 (LWP 4506) 0x00714422 in __kernel_vsyscall () 4 Thread 0x3fb9b70 (LWP 4510) 0x00714422 in __kernel_vsyscall () 3 Thread 0xa141b70 (LWP 4511) 0x00714422 in __kernel_vsyscall () 2 Thread 0x3877b70 (LWP 4514) 0x00714422 in __kernel_vsyscall () * 1 Thread 0xec26f0 (LWP 4493) 0x08110da0 in mono_object_new_specific ()
+ Trace 223302
Thread 2 (Thread 0x3877b70 (LWP 4514))
================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= Abandon
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
In particular, you'll want the libmtp debug package(s) -- might be called libmtp-debug or -dbg or something similar.