Hi people. I'm having an strange behaviour when connecting a generic usb media player. Im using Amarok 1.4 Fast Forward, as installed on the latest Kubuntu version (6.06 Dapper Drake 64 bits - the exact package identifier is 2:1.4.0a-0ubuntu2), using xine engine, with a Creative Zen Nano Plus (1GB). When i connect the device into an USB plug on my System, it's identified by kde and i'm offered to mount it. However, i decided i wanted to have it mounted and dismounted by amarok when connecting and disconnecting, as per the examples in the configuration dialog for a generic media device. So i put "mount %d" in the preconnect command, and "eject %d" in the postdisconnect one, and added this line to /etc/fstab:
/dev/sda1                      /media/zen        vfat        rw,user,noauto                        0      0

But when i connect the media device, cancel kde's autoinsert dialog, and press connect, i get a popup dialog stating that i have to mount the device before connecting to it. However, if i inmediately press connect again, without doing anything else, it connects perfectly, shows me the music contained in the media player, and doesn't complain at all. And of course disconnecting afterwards works like a charm, unmounting the device. It seems like it launchs the mount command and then tries to connect to the device, but it didn't have enough time to get mounted, so it fails. Next time i press connect, the device is already mounted and so it succeeds.

I'm posting here and not filing a bug because i want to know if i'm missing something i have to do in order for this to work correctly, or if it's a known bug, or only happens to me. If you can confirm me it's a bug and it's not known already i'll go on and file it. I've been searching for one on kde's bug tracking system as linked on amarok's front page, but couldn't manage to find one, so my apologies if it's there.

Thanks in advance

Same behaviour for me herei in amarok-svn built on 21 June.

Thanks for your confirmation, i'll go on and file a bug.

Edit: It seems there was already one filed:
http://bugs.kde.org/show_bug.cgi?id=128334
Thanks for your time though, i'm posting a comment on the bug with a reference to this thread.