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 660681 - MTP device detection fails with banshee-2.2
MTP device detection fails with banshee-2.2
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: Device - MTP
2.2.0
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2011-10-02 09:35 UTC by Chris Vine
Modified: 2020-03-17 09:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debug log from banshee-2.2.1 (10.67 KB, text/plain)
2011-11-28 23:30 UTC, Chris Vine
Details
Output from udevadm info --export-db (156.61 KB, text/plain)
2011-11-28 23:31 UTC, Chris Vine
Details
Output from gvfs-mount --list (136 bytes, text/plain)
2011-11-28 23:32 UTC, Chris Vine
Details

Description Chris Vine 2011-10-02 09:35:28 UTC
With version 2.2, banshee fails to detect my Samsung YP-U3 MTP "stick", which means I can't use that version to put mp3's on it or take them off.

Bansee-2.0 (and earlier versions) worked fine, so this may be caused by the switch to gudev-sharp.  I notice that banshee-2.0 also fails to detect the MTP device merely by gudev-sharp being installed.  Once I uninstall gudev-sharp, banshee-2.0 works fine again.

This is as tested with libgdiplus-2.10, mono-2.10.6, gtk-sharp-2.12.11, mono-addins-0.6.2, gio-sharp-2.22, gnome-sharp-2.24.2, gtk-sharp-beans-2.14.1, dbus-sharp-0.7.0, dbus-sharp-glib-0.5.0, boo-0.9.3.3457, gdata-sharp-1.7.0.1, gudev-sharp-1.0-0.1, gkeyfile-sharp-0.1, taglib-sharp-2.0.4.0 and mono-zeroconf-0.9.0.
Comment 1 David Nielsen 2011-11-28 16:30:54 UTC
Please try following this guide to determine the source of the MTP detection problem with your device.

http://mail.gnome.org/archives/banshee-list/2011-November/msg00036.html
Comment 2 Chris Vine 2011-11-28 23:27:16 UTC
1.  The device is not automounted by the system.  The device is not recognised by banshee-2.2.1 whether plugged in after or before banshee is started.

2.  The device is detected by mtp-detect.  mtp-detect reports it as a Samsung YP-U3, Ver 1.13 EU.  If starting banshee-2.2.1 after running mtp-detect, banshee still does not detect the device.

3.  As I have already reported, the device IS correctly detected by banshee-2.0.1, provided that gudev-sharp is not installed.

4.  I attach a banshee debug log, although it should be noted that plugging in or unplugging the MTP stick
Comment 3 Chris Vine 2011-11-28 23:29:19 UTC
Sorry, some fat finger combination caused the comment to be posted part way through.  Point 4 should have said:

4.  I attach a banshee debug log, although it should be noted that plugging in
or unplugging the MTP stick produces no debug putput.   Also attached is the output of udev-adm and of gvfs-mount.
Comment 4 Chris Vine 2011-11-28 23:30:22 UTC
Created attachment 202336 [details]
Debug log from banshee-2.2.1
Comment 5 Chris Vine 2011-11-28 23:31:16 UTC
Created attachment 202337 [details]
Output from  udevadm info --export-db
Comment 6 Chris Vine 2011-11-28 23:32:03 UTC
Created attachment 202338 [details]
Output from gvfs-mount --list
Comment 7 David Nielsen 2011-11-29 14:57:31 UTC
thank you, I believe that is all the information needed to examine the issue. I adding Alan McGovern to CC as he knows all the sufferings of mtp.
Comment 8 André Klapper 2020-03-17 09:24:02 UTC
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.