GNOME Bugzilla – Bug 612890
Banshee doesn't detect Motorola Droid
Last modified: 2010-03-26 22:42:30 UTC
Steps to reproduce: Plug in a Droid. Open Banshee. Expected: Banshee detects the Droid so that it can sync with it. Actual: It doesn't detect it.
Forgot to include my distro. I tested this on three computers. 2 running Ubuntu 9.10, and 1 running Lucid Lynx Alpha 3.
What's the output of running 'lsusb' ?
Bus 001 Device 007: ID 22b8:41db Motorola PCS And a bunch of other stuff that I didn't include (I can if you need it, but I figured that was the relevant line).
Can you run Banshee from a terminal with --debug with your device plugged in, and attach the log output here? Also, you do know that when you plug in Android phones such as the droid, you have to select on the phone to mount its drive before apps like Banshee can access it, right?
Created attachment 156206 [details] Banshee run with --debug
There you go. Yes, I mounted the Droid before running Banshee. And I checked that Ubuntu detects it as a 16GB flash drive.
[Warn 11:42:58.418] Service `Banshee.Hardware.HardwareManager' not started: No HardwareManager extensions could be loaded. Hardware support will be disabled. it sounds like you're missing the HAL backend. I'm CC'ing the Ubuntu packager; hyperair, do you know why he'd be missing the HAL backend (Banshee.Hal.dll)?
I believe HAL was removed from Ubuntu 10.04 in favor of DeviceKit. See here <http://www.ubuntu.com/testing/lucid/alpha3#Hal%20removal>
My understanding is while it's no longer installed by default, it's still available (and Banshee should still depend on it until the udisks work is finished).
It is installed by default, but I think it isn't started by default. Starting it (sudo start hal) should do the trick. But I'm not running Lucid, so I can't give any guarantees on this.
I tried that on Ubuntu 9.10 and it said that hal was already running. Then I tried it on Lucid and it says "start: Unknown job: hal". Any suggestions?
I was able to start HAL with "sudo hald --daemon=yes". I then started Banshee, but it still doesn't work. I will attach a new log file.
Created attachment 156247 [details] Banshee on lucid after starting HAL
I just tested this with the new Banshee 1.5.7, and Lucid Beta 1, and still have the same problem. Let me know if you need me to run any more tests.
I committed a couple patches the other day that should fix this on Lucid (and did in my testing): 1) Reflect DeviceKit being renamed to UDisks 2) Start the HAL service via DBus if needed The patches aren't in any release yet, but you could test by checking out Banshee from git. I'm going to mark as fixed; re-open when you test it doesn't resolve the issue for you.
I just checked out the latest git and built it on Lucid and it doesn't seem to have fixed this for me. I wasn't able to get it to build on Karmic because I couldn't find the libgconf2.0-cil-dev package. I checked that lsusb showed the device, and that Lucid was detecting it as a flash drive, before starting banshee. So, I'm reopening this, and attaching the output.
Created attachment 157092 [details] output from GIT Mar 25 2010 10:30am
In Karmic, it's libgconf2.0-cil. You can get the necessary build-depends by adding the deb-src line for the banshee-daily PPA to sources.list and running apt-get build-dep banshee.
I built it on Karmic, and the fix seems to work fine there. So it looks like this is limited to Lucid now.
I don't think Karmic had this problem to begin with. HAL is started by default on Karmic.
Karmic does have this problem. See the earlier posts in my bug report.
Marking this fixed. I discovered this was just a problem with my Lucid installation. I'm not sure what was wrong, but I reinstalled today and now it works.