I can confirm this bug exactly as neoeno described it. His workaround worked for me as well. But the behavior of amarok should be change, so that no workaround is needed.
My amarok version: Version 2.2.0 (KDE 4.3.2)
I can confirm this bug exactly as neoeno described it. His workaround worked for me as well.
But the behavior of amarok should be change, so that no workaround is needed.
My amarok version:
Version 2.2.0 (KDE 4.3.2)