GNOME Bugzilla – Bug 599123
Banshee can no longer read MTP Zen Micro
Last modified: 2010-09-06 23:04:09 UTC
On upgrading to 1.5.0,from 1.4.3, Banshee can no longer read from MTP Zen Micro. Zen appears in Banshee but as empty, or empty except one track. Shows apparently correct Zen disk usage on bar display, but shows data as 'other', instead of 'audio', which it is. Can sporadically export tracks to Zen, but Banshee does not remember those tracks on next Banshee session. Occasional Banshee crash/self-termination. Zen Micro worked quite well on 1.4.3, on 1.5.0 there is no usable functionality. Have tried reinstalling from Banshee website one-click/Suse 11.1 repo, but cannot regain MTP functionality nor downgrade back down to 1.4.3 using these. Tried to produce log using recommended method but nothing appeared.
Here, I am using a Sony E430 player and openSUSE 11.1. Banshee version 1.4.3 was freezing and crashing when the MTP player was connected. Banshee version 1.5.1 (now with separate dmp plugins packages) does not even notice when the MTP player is plugged. The --debug-addins switch does not provide any output about MTP.
This may be the same as Bug 574091, though there they experience the problem with Banshee 1.4.3. Here, mtp-tracks from command line works OK with my player.
Bulk changing the assignee to banshee-maint@gnome.bugs to make it easier for people to get updated on all banshee bugs by following that address. It's usually quite apparent who is working on a given bug by the comments and/or patches attached.
I have since discovered that the tracks Banshee 1.5.1 exported to Zen Micro as mentioned above do not play on Micro -- Micro says 'Playback error'.
I think I'm getting similar errors with a Creative Zen X-FI. I'm using Banshee 1.5.1 and libmtp8 0.3 from the openSUSE 11.2 repos (although I've tested libmtp 1.0 from Packman and libmtp8 1.0.1 from the GPhoto repo) and keep getting messages such as: PTP_ERROR_IO: Trying again after re-initializing USB interface [Warn 19:46:13.762] Caught an exception - Object reference not set to an instance of an object (in `Mtp') at (wrapper unknown) Mtp.TrackStructtrToStructure (intptr,object) at (wrapper managed-to-native) System.Runtime.InteropServices.MarshaltrToStruct ure (intptr,System.Type) at Mtp.MtpDevice.GetAllTracks (Mtp.ProgressFunction callback) [0x00000] at Banshee.Dap.Mtp.MtpSource.LoadFromDevice () [0x00000] and PTP_ERROR_IO: Trying again after re-initializing USB interface inep: usb_get_endpoint_status(): Input/output error outep: usb_get_endpoint_status(): Input/output error usb_clear_halt() on IN endpoint: Numerical result out of range usb_clear_halt() on OUT endpoint: Numerical result out of range usb_clear_halt() on INTERRUPT endpoint: Numerical result out of range LIBMTP PANIC: Could not open session! (Return code 767) Try to reset the device. [Warn 20:29:56.163] Caught an exception - Connecting (in `Mtp') at Mtp.Error.CheckError (ErrorCode errorCode) [0x00000] at Mtp.MtpDevice.GetConnectedDevices (System.IntPtr& list) [0x00000] at Mtp.MtpDevice.Detect () [0x00000] at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x00000] With the former being the most common. Copying to the device always freezes at the end of the first track, which then appears on the device as a file name but hits a "playback error" when you try to play it back. I was also getting the "everything showing as other" issue as well before I formatted the device through the internal Zen menus to start my player from scratch.
Ahhh, I'm on a 64-bit system, so it looks like I might be hitting bug594191 - unfortunately it doesn't seem to have been committed yet, which explains why even using the 'bleeding edge' Banshee 1.5.2 from the special Banshee OBS repo didn't help.
It's also possible you're hitting a known limitation of the gphoto2 gvfs backend which completely breaks banshee's ability to use a freshly connected device. If you have issues getting your device to show up in banshee, try: 1) Quit banshee 2) Connect your device and wait about 10 seconds for libgphoto to try and mount it. 3) Start banshee up. I'm going to close this bug for now. If you can still reproduce these issues with 1.7.5 and libmtp 1.0.3, please reopen the bug. However your issues should be fixed.