Bug 191988

Summary:	Amarok prevents portable music players from mounting in KDE 4
Product:	[Applications] amarok	Reporter:	Rob Hasselbaum <rob>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	aikawarazuni, jook_roberts
Priority:	NOR
Version First Reported In:	2.0.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rob Hasselbaum 2009-05-08 03:29:58 UTC

Version:           2.0.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-11-generic

In Kubuntu 9.04, leaving Amarok running in the system tray prevents KDE from recognizing that I've plugged in my Sansa e260 portable music player. Steps to reproduce:

(1) Start Amarok.
(2) Plug music player into USB slot.

Observe that the player does not appear in the KDE Device Notifier and is not mounted. However, it does appear in "/var/log/messages" and in the output of "lsusb". If I plug in the player after quitting Amarok, it shows up in the Device Notifier right away and cam be opened in Dolphin.

I didn't think Amarok 2.0.2 even supported portable music players.

Comment 1 Rob Hasselbaum 2009-05-08 03:31:48 UTC

See related forum thread: http://kubuntuforums.net/forums/index.php?topic=3103005.

Comment 2 jook_roberts 2009-05-08 05:12:45 UTC

Also stops you from mounting flash drives.

Comment 3 Alejandro Wainzinger 2009-05-18 02:12:06 UTC

Amarok does not automount anything.  It does, however, autoconnect to already-mounted devices, and to attached MTP devices.

My iPod, which is essentially a usb hard drive, gets picked up by the device notifier applet, and I have to mount it using the applet before Amarok recognizes the device.

I'm going to assume you have your player in MSC/UMS mode and not in MTP mode when plugged in, because that's the only reason it should not be getting seen by the device notifier applet.

I am running Kubuntu 9.04 and can't reproduce this, but I'm running Amarok from trunk.  Perhaps it's a 2.0.2 bug, please upgrade to the latest Amarok 2.1 beta and see if it's still occurring.  If so, reopen the bug.