GNOME Bugzilla – Bug 690082
Banshee freeze when connecting a Samsung Galaxy S3
Last modified: 2020-03-17 09:59:42 UTC
When I connect a my Samsung Galaxy S3 banshee get freeze and I need to kill it through System Monitor (or xkill) and then I cannot mount the device (until disconnected and connected again without running Banshee). If banshee isn't running, I can mount it an browse it normally. This is what happened if I run it from console. jabellota@gl-se-pc015:~$ banshee [Info 10:20:03.996] Running Banshee 2.6.0: [Ubuntu 12.04.1 LTS (linux-gnu, i686) @ 2012-10-04 07:17:07 UTC] [Info 10:20:11.186] Updating web proxy from GConf [Info 10:20:11.579] All services are started 5,155227 [Info 10:20:14.973] nereid Client Started [Info 10:20:15.338] GStreamer version 0.10.36.0, gapless: True, replaygain: True [Info 10:20:15.474] AppleDeviceSource is ignoring unmounted volume ghcsamba [Warn 10:20:15.538] Caught an exception - System.ArgumentNullException: Argument cannot be null. (in `mscorlib') at System.Int32.Parse (System.String s, NumberStyles style, IFormatProvider provider) [0x00000] in <filename unknown>:0 at System.Int32.Parse (System.String s, NumberStyles style) [0x00000] in <filename unknown>:0 at Banshee.Hardware.Gio.UsbDevice.GetVendorId (IUsbDevice device) [0x00000] in <filename unknown>:0 at Banshee.Hardware.Gio.UsbDevice.get_VendorId () [0x00000] in <filename unknown>:0 at Banshee.Dap.Karma.KarmaSource.IsKarma (IDevice dev) [0x00000] in <filename unknown>:0 at Banshee.Dap.Karma.KarmaSource.DeviceInitialize (IDevice dev) [0x00000] in <filename unknown>:0 at Banshee.Dap.DapService.FindDeviceSource (IDevice device) [0x00000] in <filename unknown>:0 [Warn 10:20:58.444] Forcefully breaking out of RCS loop b/c change in total_width less than 1.0 [Warn 10:22:12.061] Failed to load media-player-info file for 1 Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. [Warn 10:22:13.627] Failed to load media-player-info file for 1
What distro and version? If I post a patch, would you know how to test it? (You would need to compile banshee yourself)
Ubuntu 12.04.1 LTS and Banshee 2.6.0-1ubuntu1~hyper1+precise. And yes, I can test it. I'm programmer and I have knowledge about compiling it from sources (although not a lot of knowledge :) ).
Ok great. I see two problems here: a) device detection: something is happening that prevents media-player-info integration to work. For this, it would be helpful if you could test patching banshee with this simple change that I'm posting here as an attachment. b) UI freeze: even if the problem (a) shouldn't happen, that failure shouldn't cause Banshee to hang. To debug this, you will need to install this little tool: https://github.com/slluis/gui-thread-check More technical details: About a): first make sure you manage to compile Banshee from git master, following the instructions here: http://banshee.fm/download/development/ . If you manage to do it, then next step is applying this patch. About b): first find out where mono is installed. Normally it's in /usr. To find out, type "which mono", if the result is /usr/bin/mono, then the prefix is definitely /usr. You need to know this information before installing gui-thread-check, because to install it you will specify the same prefix, example: git clone https://github.com/slluis/gui-thread-check.git cd gui-thread-check ./autogen.sh --prefix=/usr make sudo make install So after you've finished a) and b), it means you have a patched banshee from the latest sources from git. You would then just need to run in installed mode (via "make run", no need to install), and hopefully with that you will get a much better error log that you can copy+paste here (or attach as a file) so we can figure out what's going on and what to fix! Thanks in advance. If you have any doubts, let me know here, or in irc://irc.gnome.org/banshee
Created attachment 231348 [details] [review] debug patch Oops, this is the patch I was mentioning, forgot to attach it.
Created attachment 231356 [details] Console output after appling the patch and trying to compile I have tried to compile with the diff applied but it have errors. Before applying it I have compile and run it without problem.
Created attachment 231370 [details] [review] debug patch v2 Oops, sorry, I thought the C# compiler was going to infer the "ToString" there. Try with this one.
Created attachment 231396 [details] It's the log when you plug the S3 and you have running banshee. I have run banshee with "make run > whenRuning.log" and bellow is the output of the console. As I have seen in the log that it will try more times, I have waited and finally (after 4 attemps more as seen in the log, about 10 minutes) banshee become unfreeze again and can be used. After this I have close it (in the log this are all message after "[1 Debug 18:30:52.412] Service disposed (NotificationAreaService)" message. Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt
Created attachment 231398 [details] log when putting galaxy and running banshee I have run banshee with "make run > whenRuning.log" and bellow is the output of the console. As I have seen in the log that it will try more times, I have waited and finally (after 4 attemps more as seen in the log, about 10 minutes) banshee become unfreeze again and can be used. After this I have close it (in the log this are all message after "[1 Debug 18:30:52.412] Service disposed (NotificationAreaService)" message. Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt
Ups, double posting. I have also see that if you chose PTP (Camera protocol?) instead of MTP (Multimedia protocol?) as USB connection type it haven't had any problems with banshee. Did not banshee compatible with MTP?
Sorry it took so long to reply! (In reply to comment #9) > Did not banshee compatible with MTP? Banshee has a MTP extension. And it actually has received recently some fixes, so can you pull again from master and try again? BTW I don't see in your logs that gui-thread-check is loaded correctly, did you install it in the same prefix as Mono like I advised?
Created attachment 234002 [details] It's the log when I start banshee and have the S3 pluged in.
Yes I have installed it as you said how to do it. Also I have updated the S3 to Android 4.1.2 and also updated banshee to the last git version. Now when I connect the android (without banshee opened) a dialog appear with the next message: "No se pudo montar SAMSUNG_Android Error al inicializar la cámara: -60: No se pudo bloquear el dispositivo" in English maybe something as: "SAMSUN_Android can't be mounted Error at camera initialization: -60: device can't be blocked" And then when I start banshee this is what is write in the console: jabellota:~/Proyectos/banshee/banshee$ make run > whenRunning.log Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Also see the attachment is the log.
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.