Registered Member
|
Hi,
I have a somewhat weird problem with Amarok 2 and my Rockbox player. Here's what happens: Amarok is not running, I plug in the player. dmesg says
It detects correctly that it is a mass-storage USB device and lists the partitions. The device shows up in KDE4's device notifier. But if I now start Amarok, my player gets removed from the device notifier and dmesg now says:
If I plug in the player while Amarok is running, I get the same message as above and the player never shows up in the device manager. So far, I failed to find any explanation for this behavior or any solution to my problem. Other (non-media-player) USB devices work just fine with Amarok running. Any hints what is going wrong here? Thanks a lot, Marcel |
Manager
|
I think maybe you're running an older version of Amarok as I had a similar issue with my RockBox. I think it was resolved in the 2.1 release.
|
Registered Member
|
I have this problem consistently for a while, including 2.2.1, and now running the latest beta from Debian Experimental.
|
Registered Member
|
Answering my own question, it seems hal is reporting the device as mtp for some reason. Amarok then tries to automatically connect to it which of course does not work and somehow prevents it from being listed as a USB storage device afterwards.
I fixed this for the moment by removing all Sansa-related entries from /usr/share/hal/fdi/information/20thirdparty/20-libmtp8.fdi (that's for Debian. I heard there might be similar entry in gphoto.fdi if present). Not elegant, but it works for me. |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]