After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574091 - No tracks are shown in the Music Library of my MTP Device
No tracks are shown in the Music Library of my MTP Device
Status: RESOLVED INCOMPLETE
Product: banshee
Classification: Other
Component: Device - MTP
1.4.2
Other All
: Normal major
: 1.x
Assigned To: Banshee Maintainers
Gabriel Burt
Depends on:
Blocks:
 
 
Reported: 2009-03-04 15:32 UTC by Christopher Perrin
Modified: 2010-03-21 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christopher Perrin 2009-03-04 15:32:02 UTC
Please describe the problem:
When I plug in my MTP device ( Creative Zen Vision:M 30 GB ), banshee loads the Device but now tracks are shown. This Happens since I tryed to sync up tracks to my Device.

The Status page shows that all tracks are still there but when I click on music, everything is empty.

I have this problem since I tried to load some tracks from banshee to my device.

Amarok, Rhythmbox as well as the device itself can still see all the tracks.

Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Gabriel Burt 2009-06-02 22:44:12 UTC
Can you try with Banshee 1.4.3 or 1.5.0?  There have been quite a few MTP fixes
Comment 2 Luca Wehrstedt 2009-08-28 20:57:02 UTC
I'm using banshee 1.4.3 and I'm having a similar issue. I've loaded all my tracks using rhythmbox (many different versions) and the player sees all the tracks and plays them without any problems.

Banshee recognizes the player but doesn't show any tracks. Instead, in the device tab, it says that the player only contains "other" data: no music and no video.

I have a Creative ZEN 4 GB, with a recent firmware and I'm using libmtp 1.0.0 under gentoo
Comment 3 Luca Wehrstedt 2009-08-28 20:58:56 UTC
Could it be related to bug #577178?
Comment 4 nyall 2009-09-04 15:44:30 UTC
Libmtp 1.0.0 seems to have broken mtp connectivity with banshee. The device can connect, but no tracks are shown on it. 
Running banshee-1 --debug results in

[Debug 11:42:23.160] Found DAP support (Banshee.Dap.Mtp.MtpSource) for device Pipface
[Warn  11:42:23.403] Caught an exception - Object reference not set to an instance of an object (in `Mtp')
  at (wrapper unknown) Mtp.TrackStruct:PtrToStructure (intptr,object)
  at (wrapper managed-to-native) System.Runtime.InteropServices.Marshal:PtrToStructure (intptr,System.Type)
  at Mtp.MtpDevice.GetAllTracks (Mtp.ProgressFunction callback) [0x0001d] in /home/nyall/Sources/banshee/src/Libraries/Mtp/Mtp/MtpDevice.cs:183 
  at Banshee.Dap.Mtp.MtpSource.LoadFromDevice () [0x0001a] in /home/nyall/Sources/banshee/src/Dap/Banshee.Dap.Mtp/Banshee.Dap.Mtp/MtpSource.cs:166
Comment 5 onip 2009-09-16 08:52:32 UTC
downgrading to libmtp-0.3.7 made banshee (git) work again.
Comment 6 Gabriel Burt 2009-10-27 20:16:22 UTC
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.
Comment 7 Alan McGovern 2009-12-23 17:10:57 UTC
Christopher, if you're on a 64bit system with libmtp >= 1.0.0 you're after hitting bug #594191. If that's the case, let me know and I'll close this bug as a dupe. There is also a fix attached to bug #594191 which you could test.

Everyone else: You're all describing bug #594191, so please take further discussion to that bug and also test the fix if possible.
 
Thanks,
Alan.
Comment 8 Christopher Perrin 2009-12-23 20:54:28 UTC
I'm not on a 64-bit system. I am not using libmtp >= 1.0.0 I'm still on Ubuntu 9.04 so I'm using libmtp 0.3.0 . I will update this if I have managed to get libmtp 1.0.1 .

I'm using Banshee 1.5.0
Comment 9 Bertrand Lorentz 2010-03-21 17:24:29 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!