Hey, what a coincidence, I had the Now Playing widget on my desktop too!

I didn't have any particular CPU issues that I noticed. (Though I have a pretty old machine, so _always_ have CPU issues, so it might have got lost in the noise... )

I have tended to get quite a few "random" plasma lock-ups/crashes. Presumed it was just pre-release software...

Good to have Amarok back anyway. Impressive work grrrv and uicz, thank you!

I can confirm both the skipping behavior with 'now playing' plasmoid on my desktop and the apparent fix by removing the plasmoid.

It's a known issue - when a track starts playing that is shorter than the previously playing track, the now playing applet will cause it to skip to the end (not just in Amarok, but in any media player).

It's fixed in 4.2.2.

hey, one more grateful reader of this topic

still found no answer to the skipped tracks. Tracks with e.g. the letter è in the filename wil be skipped by amarok. I'm using Amarok v 2.3 xine backend on KDE 4.3 (factory) openSuse 11.2. Changing phonon to g-streamer backend does not help. Xine is not the problem, it wil play the file without any problem.
Tried to change from mysql db to internal database, but problem remains. changing the filename from xxxxxèxx.mp3 to xxxxxexx.mp3 helps to play the file, but is not an acceptable solution to me.

You should try with a more recent KDE SC version, since there were some changes in Phonon since. Could you try again with KDE SC 4.4.2?

Roble wrote:Tracks with e.g. the letter è in the filename wil be skipped by amarok. I'm using Amarok v 2.3 xine backend on KDE 4.3 (factory) openSuse 11.2. Changing phonon to g-streamer backend does not help. Xine is not the problem, it wil play the file without any problem.
Tried to change from mysql db to internal database, but problem remains. changing the filename from xxxxxèxx.mp3 to xxxxxexx.mp3 helps to play the file, but is not an acceptable solution to me.

Same issue here with Kubuntu 10.04 and Amarok 2.3. Any filename or directory with extended characters in it causes Amarok to not be able to open or play it. Not sure whether the characters in question are UTF8, UTF16 or some extended ASCII value but it does make me nervous when an odd file name is enough to break Amarok's I/O functions. Usually when you see that sort of thing it means that you have a file escaping problem somewhere and improper escaping can lead to security vulnerabilities.

This happens from within the embedded file manager with directories so perhaps it is a KDE issue?

Hopefully this does not represent a more serious vulnerability.

Cheers