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 664855 - Galaxy Nexus (MTP, phone) doesn't show up in Banshee
Galaxy Nexus (MTP, phone) doesn't show up in Banshee
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Device - MTP
git master
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
: 664856 667981 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-11-26 02:02 UTC by Chow Loong Jin
Modified: 2013-03-16 11:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
udevadm info --export-db with phone connected (138.06 KB, text/plain)
2011-11-28 18:04 UTC, Martijn van de Streek
Details
Output of "gvfs-mount --list" with phone connected (544 bytes, text/plain)
2011-11-28 18:04 UTC, Martijn van de Streek
Details
Output of "banshee --debug" with phone connected (50.68 KB, text/plain)
2011-11-28 18:06 UTC, Martijn van de Streek
Details
banshee --trace=N:Banshee.Hardware.Gio --redirect-log (23.65 KB, text/plain)
2011-12-13 17:26 UTC, Martijn van de Streek
Details

Description Chow Loong Jin 2011-11-26 02:02:04 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/896376

I have a new phone, but it doesn't show up in Banshee. I've even recompiled libmtp to add the device ID, but that didn't help.

As the same thing happens with my Xoom tablet (also an Android device), which is included in the "unpatched" libmtp, I think this is a Banshee bug.

The MTP plugin is enabled.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Fri Nov 25 19:45:32 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803)
ProcEnviron:
 PATH=(custom, user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: No upgrade log present (probably fresh install)
Comment 1 Chow Loong Jin 2011-11-26 02:08:03 UTC
Um, whoops, looks like I filed a duplicate in 664856.
Comment 2 Bertrand Lorentz 2011-11-27 18:08:57 UTC
*** Bug 664856 has been marked as a duplicate of this bug. ***
Comment 3 David Nielsen 2011-11-28 16:30:33 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

Note, Xoom support is tracked in another bug already so please constrain this report the Galaxy Nexus: https://bugzilla.gnome.org/show_bug.cgi?id=647506
Comment 4 Martijn van de Streek 2011-11-28 18:04:04 UTC
Created attachment 202313 [details]
udevadm info --export-db with phone connected
Comment 5 Martijn van de Streek 2011-11-28 18:04:35 UTC
Created attachment 202314 [details]
Output of "gvfs-mount --list" with phone connected
Comment 6 Martijn van de Streek 2011-11-28 18:06:20 UTC
Created attachment 202315 [details]
Output of "banshee --debug" with phone connected

Note that attaching/detaching the phone doesn't seem to do anything. Or at least, nothing is getting logged by Banshee.
Comment 7 Martijn van de Streek 2011-11-28 18:07:07 UTC
As mtpfs and mtp-detect both work, I'm guessing there's a bug in Banshee's MTP support.
Comment 8 Martijn van de Streek 2011-11-28 18:09:00 UTC
My phone is the "Samsung Galaxy Nexus", I9250 (European model)

  idVendor           0x04e8 Samsung Electronics Co., Ltd
  idProduct          0x685c 

It's running Android 4.0.1 (build ITL41D).
Comment 9 Martijn van de Streek 2011-11-28 18:25:39 UTC
I've added several calls to Log.Debug("Hello!") around MtpDevice.Detect() in src/Dap/Banshee.Dap.Mtp/Banshee.Dap.Mtp/MtpSource.cs, but they are never logged (not during startup, and not on device connect/disconnect)
Comment 10 David Nielsen 2011-11-28 21:56:53 UTC
Adding the mighty Alan McGovern to CC for input.
Comment 11 Martijn van de Streek 2011-12-13 17:26:07 UTC
Created attachment 203356 [details]
banshee --trace=N:Banshee.Hardware.Gio --redirect-log
Comment 12 Martijn van de Streek 2012-01-07 07:48:25 UTC
I've managed to get the device to show up in Banshee by adding it to the music-players.h in libgphoto2.

But now banshee crashes "in native code". I'll try to get a stack trace.
Comment 13 Martijn van de Streek 2012-01-07 07:52:05 UTC
Stacktrace:

  at (wrapper managed-to-native) object.__icall_wrapper_mono_string_new_wrapper (intptr) <IL 0x0000d, 0xffffffff>
  at (wrapper unknown) Mtp.FolderStruct.PtrToStructure (intptr,object) <IL 0x0005a, 0xffffffff>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void_intptr_object (object,intptr,intptr,intptr) <IL 0x0005c, 0xffffffff>
  at (wrapper managed-to-native) System.Runtime.InteropServices.Marshal.PtrToStructure (intptr,System.Type) <IL 0x0000e, 0xffffffff>
  at Mtp.Folder.GetRootFolders (Mtp.MtpDevice) [0x00019] in /build/buildd/banshee-2.3.3/src/Libraries/Mtp/Mtp/Folder.cs:124
  at Mtp.MtpDevice.GetRootFolders () [0x00000] in /build/buildd/banshee-2.3.3/src/Libraries/Mtp/Mtp/MtpDevice.cs:183
  at Mtp.MtpDevice.SetDefaultFolders () <0x00027>
  at Mtp.MtpDevice..ctor (Mtp.MtpDeviceHandle,Mtp.MtpDeviceStruct) [0x00036] in /build/buildd/banshee-2.3.3/src/Libraries/Mtp/Mtp/MtpDevice.cs:132
  at Mtp.MtpDevice.Connect (Mtp.RawMtpDevice) [0x00021] in /build/buildd/banshee-2.3.3/src/Libraries/Mtp/Mtp/MtpDevice.cs:274
  at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (Banshee.Hardware.IDevice) [0x000c6] in /build/buildd/banshee-2.3.3/src/Dap/Banshee.Dap.Mtp/Banshee.Dap.Mtp/MtpSource.cs:104
  at Banshee.Dap.DapService.FindDeviceSource (Banshee.Hardware.IDevice) [0x00025] in /build/buildd/banshee-2.3.3/src/Dap/Banshee.Dap/Banshee.Dap/DapService.cs:159
  at Banshee.Dap.DapService/MapDeviceJob.Run () [0x000d3] in /build/buildd/banshee-2.3.3/src/Dap/Banshee.Dap/Banshee.Dap/DapService.cs:215
  at Banshee.Kernel.Scheduler.ProcessJobThread () [0x00080] in /build/buildd/banshee-2.3.3/src/Core/Banshee.Core/Banshee.Kernel/Scheduler.cs:233
  at System.Threading.Thread.StartUnsafe () <IL 0x00021, 0x00071>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <IL 0x0004e, 0xffffffff>

Native stacktrace:

	banshee() [0x49118a]
	banshee() [0x4e063f]
	banshee() [0x41b187]
	/lib/x86_64-linux-gnu/libpthread.so.0(+0x10060) [0x7f48aabba060]
	/lib/x86_64-linux-gnu/libc.so.6(+0x128c7f) [0x7f48aa933c7f]
	banshee(mono_string_new+0x1c) [0x56177c]
	[0x41bc86ba]
Comment 14 André Klapper 2012-01-16 10:37:29 UTC
*** Bug 667981 has been marked as a duplicate of this bug. ***
Comment 15 olivier dufour 2012-08-13 10:18:37 UTC
have you try with last git?
I have commit a fix for this phone in july and it work on my phone:
http://git.gnome.org/browse/banshee/commit/?id=cbafd2e717d0c07940c329b137c97a7f08377249
Comment 16 Martin Stjernholm 2012-08-19 14:47:35 UTC
I've tested that patch in 2.4.1 (Ubuntu Precise packaging), and I've had some limited success:

The device now shows in Banshee, sometimes after a long delay (on the order of several minutes). It doesn't show any stored media though, and adding new media to it fails with "LIBMTP_Send_Track_From_File_Descriptor(): subcall to LIBMTP_Send_Track_From_File_Descriptor failed."

However, I suspect those problems are due to libmtp than Banshee, since I'm afflicted by https://bugs.launchpad.net/ubuntu/+bug/903422.
Comment 17 Tobias Mueller 2013-03-16 11:43:25 UTC
Let's assume this to be FIXED then. Please reopen if it's not.