If I leave Amarok playing for any length of time (I guess, 20 minutes?) then it will eventually log me out entirely, killing my whole KDE session.
This is rather hard to troubleshoot because, obviously, the KDE bug wizard isn't launched!

I'm not really sure how to troubleshoot this. Would it be possible to start Amarok from the command line and have any output saved to a file?

And once again:
Distribution/KDE/Amarok versions?

Does your session crash or are you logged out automagically?
Are you working while it happens or is your system idle (except amarok)?
Move the script folder out of the way.
Any timer software (kalarm, kshutdown) running?

More infos provide faster solutions.

m0nk

Distribution: Kubuntu
KDE: 4.3.1
Amarok: 2.1

Does your session crash or are you logged out automagically?
I'm not sure how to tell the difference. The computer returns me to kdm, where I have to sign in again from scratch.

Are you working while it happens or is your system idle (except amarok)?
The system is idle.

Move the script folder out of the way.
I've moved

Code: Select all

~/.kde/share/apps/amarok/scripts

elsewhere, will re-test, and report back.
Any timer software (kalarm, kshutdown) running?
No.

To report back: Moving the scripts folder out of the way did not help. Amarok still kills my whole KDE login after a short period of playing.
What can I do to troubleshoot this?

asktoby wrote:If I leave Amarok playing for any length of time (I guess, 20 minutes?) then it will eventually log me out entirely, killing my whole KDE session.
This is rather hard to troubleshoot because, obviously, the KDE bug wizard isn't launched!

I'm not really sure how to troubleshoot this. Would it be possible to start Amarok from the command line and have any output saved to a file?

With "killing KDE session" you probably mean that your X-Server has crashed. This is usually caused by bad graphics drivers.

Check for updates of your graphics driver.

asktoby wrote:To report back: Moving the scripts folder out of the way did not help. Amarok still kills my whole KDE login after a short period of playing.
What can I do to troubleshoot this?

1. After the crash, don't log in graphically, but change to a terminal.
Log in and do

Code: Select all

less .xsession-errors

.
2. Also check /var/log/Xorg.0.log.old (the backup) and Xorg.0.log for X and/or driver related issues.
It's very unlikely, that Amarok 2 crashes the whole Xsession.
3. Set your windeco and style to "default", means oxygen or something like that.

Ever tried to leave your system idle without running Amarok to see, if it crashes, too?

m0nk

If you have Desktop Effects enabled, try disabling them also.