Hi there,

I'm having some unusual problems with the latest release of Amarok (1.4.5):

I installed from the Kubuntu repository at  'deb http://kubuntu.org/packages/amarok-145 edgy main' following instructions here: http://kubuntu.org/announcements/amarok-1.4.5.php.

On first run it was fine - clicked the icon, it started up, nice and shiny, lots of great improvements 

Since then, however:

• running it from the K Menu or the launcher produces a slight blip on my CPU monitor, but nothing actually appears;
• running 'amarok' in a console produces another slight blip, but gives no output at all and again nothing happens;
• running 'amarokapp' from console starts fine, and runs without problems;
• however, if amarok is left running at shutdown (from running 'amarokapp' in console), on restart KDE tries to launch it again, and it crashes and produces three crash reports to email to the relevant list.  I've sent these once, but I didn't want to swamp them with more!

I'm sort-of happy to launch from the console as 'amarokapp' (or change the shortcut to that) until the next release or an upgrade of Kubuntu fixes it, but it'd be nice to get it sorted and I guess I may not be the only one with the problem.

Anyone got any ideas or pointers?  Any help much appreciated 

Amazing app by the way - along with Firefox it's one of my most-used programs ever, many thanks!

Pete

Vital statistics:

• Distro: (k)Ubuntu Edgy
• KDE version: 3.5.6
• Amarok version: 1.4.5
• Engine: xine-engine

Try "killall -s 9 amarok". If that doesn't help, it might be a packaging problem. Please report this on the Kubuntu "launchpad" bug tracker.

Mark Kretschmann wrote:Try "killall -s 9 amarok". If that doesn't help, it might be a packaging problem. Please report this on the Kubuntu "launchpad" bug tracker.

Sorted it.

"killall -s 9 amarok" didn't work at first, but then I ran "ps -A | grep amarok" which revealed four 'amarokapp' processes running:

Code: Select all

peter@R-Daneel:~$ ps -A | grep amarok
 4910 ?        00:00:02 amarokapp
 5162 ?        00:00:00 amarokapp
 5172 ?        00:00:00 amarokapp
 5212 ?        00:00:00 amarokapp

I then ran "killall -s 9 amarokapp" which got rid of them, and now all's fine and dandy - shortcuts work, as does launching from console with "amarok". I've no idea what caused this, but it's fixed 

Many thanks for your help!

Oops, update.

Problem not quite gone; seems I slightly misdiagnosed it.

The problem only occurs on KDE startup - if Amarok was running when you log off, KDE will try to relaunch it when you log back in again. It seems it's this particular launch of Amarok which is causing problems, generating crash reports and creating the rogue 'amarokapp' processes. Whenever I start KDE having left Amarok running on shutdown, it fires up several traceback emails and I have to run the 'killall -9 amarokapp' magic. Once I do that, all manual launches/quits of Amarok work fine, but if I leave it running when I log off, the problem returns at next log in.

Any further ideas? Or is this a KDE/Kubuntu bug which should be logged with them?

Again, many thanks in advance for your help, and for this great program 

(PS - Mark, didn't realise you were the lead dev 'til I read an interview today via Digg - I feel honoured!  )