GNOME Bugzilla – Bug 554526
Banshee crashes with mono SIGSEGV when Creative Zen Vision:M is plugged in
Last modified: 2009-01-30 00:14:22 UTC
Steps to reproduce: 1. Start banshee 1. plugin creative player 3. wait for the madness Stack trace: PTP: Opening session [Debug 23:32:10.679] Found DAP support (Banshee.Dap.Mtp.MtpSource) for device Zen Vision:M Stacktrace: Native stacktrace: banshee-1 [0x817d3de] banshee-1 [0x807f78b] [0xb7f95410] Debug info from gdb: (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7cec6d0 (LWP 12204)] [New Thread 0xb0ffeb90 (LWP 12245)] [New Thread 0xb09e7b90 (LWP 12244)] [New Thread 0xb0ae8b90 (LWP 12243)] [New Thread 0xb0be9b90 (LWP 12242)] [New Thread 0xb0efdb90 (LWP 12237)] [New Thread 0xb1c7ab90 (LWP 12216)] [New Thread 0xb1d7fb90 (LWP 12215)] [New Thread 0xb1e84b90 (LWP 12214)] [New Thread 0xb617fb90 (LWP 12210)] [New Thread 0xb73a9b90 (LWP 12206)] [New Thread 0xb73cdb90 (LWP 12205)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7f95430 in __kernel_vsyscall () 12 Thread 0xb73cdb90 (LWP 12205) 0xb7f95430 in __kernel_vsyscall () 11 Thread 0xb73a9b90 (LWP 12206) 0xb7f95430 in __kernel_vsyscall () 10 Thread 0xb617fb90 (LWP 12210) 0xb7f95430 in __kernel_vsyscall () 9 Thread 0xb1e84b90 (LWP 12214) 0xb7f95430 in __kernel_vsyscall () 8 Thread 0xb1d7fb90 (LWP 12215) 0xb7f95430 in __kernel_vsyscall () 7 Thread 0xb1c7ab90 (LWP 12216) 0xb7f95430 in __kernel_vsyscall () 6 Thread 0xb0efdb90 (LWP 12237) 0xb7f95430 in __kernel_vsyscall () 5 Thread 0xb0be9b90 (LWP 12242) 0xb7f95430 in __kernel_vsyscall () 4 Thread 0xb0ae8b90 (LWP 12243) 0xb7f95430 in __kernel_vsyscall () 3 Thread 0xb09e7b90 (LWP 12244) 0xb7f95430 in __kernel_vsyscall () 2 Thread 0xb0ffeb90 (LWP 12245) 0xb7f95430 in __kernel_vsyscall () 1 Thread 0xb7cec6d0 (LWP 12204) 0xb7f95430 in __kernel_vsyscall ()
+ Trace 207599
Thread 6 (Thread 0xb0efdb90 (LWP 12237))
================================================================= 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. ================================================================= zsh: abort (core dumped) banshee-1 --debug Other information: Library is more or less viewable in player, but it still says loading, then all of a sudden it SIGSEGVs. Player word before syncing code was commited, happens regardless of whether manual, automatic, or neither are checked. It seems to always reach 5846 of 5847, so it may be a bad file on my player. I'm going to try formatting it, and seeing if the problem persists.
I have this exact same problem, did the format help?
A format did not help, this bug still exists.
Could this be a duplicate of Bug #542117?
Confirm this bug still exists with 1.4.2 There was discussion on the Banshee mailing list that a work around was reformatting and installing the latest firmware. However, I use a Creative Zen Vision:M 30Gb - which creative have stopped updating the firmware for. I'm already running the most uptodate version that will ever be. :(
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 542117 ***