On Tue, 19 Oct 2010, Manuel Reimer wrote: > Alan Stern wrote: > > Evidently the "bad" program gets started by some utility running under > > X. When X is off, the player works. > > Exactly. > > I continued my tries. Starting up a plain X-server didn't trigger this > issue, so I tried with a new user and logged in to a X session with this > test user. Again, the problem didn't exist. > > Now I remembered, that I have "Amarok" in autostart of my regular user, > so I logged in with my regular user, closed Amarok and plugged my > player. With Amarok closed, the player immediately was available as > regular usb flash drive. > > After some more debugging, I tracked this problem down to "libmtp". In > /lib/udev/rules.d/90-libmtp.rules, I found my vendor/product id > combination of my player for some other player. Seems like this vendor > uses same product ID for more than one model. Either my player doesn't > work with mtp at all or something is wrong with my libmtp installation. > To disable mtp at all (don't need it), I created an empty file > /etc/udev/rules.d/90-libmtp.rules which effectively disables the > original file. Maybe the player can be switched into different modes, of which one supports mass storage and one supports mtp. > After doing so, my MP3 stick seems to work the way it should do. Noone > kills the device down while it tries to initialize the usb-storage device. > > Maybe I should contact the libmtp team to discuss with them, if they > should improve their udev rules to not match for this player. Good idea. > Thanks for your help with tracking down this issue! You're welcome. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
