Hi All,

As soon as I run Amarok just once KDE becomes ugly (I think all the widgets become transparent). To fix it I tried the following but no one fixed the problem:

1. Clicked F5 to refresh the desktop
2. Removed and added many different desktop widgets
3. Changed window styles
4. Changed themes
5. Installed latest proprietary display drivers (I'm using NVIDIA)

How can I fix this issue?

PS
The only solution for this bug is deleting the corrupted user and create a new one without running Amarok.

Screenshots
[Before running Amarok] http://img829.imageshack.us/img829/2203/snapshot1bk.png
[After running Amarok] http://img259.imageshack.us/img259/8576/snapshot2pr.png

This is not Amarok related but concerns your desktop effects. I can't tell you exactly which one it is, but that will move this thread to KWin.

I also changed the title of your thread, as there is no crash.

The desktop theme has been changed to Oxygen, try to change it back to Air in System Settings -> Workspace Appearance -> Desktop Theme.

It sounds strange that Amarok would change your desktop theme. Can you reproduce it?

Hans wrote:The desktop theme has been changed to Oxygen, try to change it back to Air in System Settings -> Workspace Appearance -> Desktop Theme.

It sounds strange that Amarok would change your desktop theme. Can you reproduce it?

You're right after switching to Air theme it worked.


By summary,

Amarok changes Desktop Theme to Oxygen just for first run.

Very unlikely, unless you have it set somewhere in a configuration file.

mbnoimi wrote:Amarok changes Desktop Theme to Oxygen just for first run.

Can you reproduce this with a fresh user?

Hans wrote:

mbnoimi wrote:Amarok changes Desktop Theme to Oxygen just for first run.

Can you reproduce this with a fresh user?

After updating Amarok and KDE this issue once again occurred after creating a fresh new user.

I regretfully must confirm this issue.
Working on a Debian based distribution with KDE, I can reproduce this for every first run of Amarok.

This is reported on Linux Mint KDE 12:
http://www.dedoimedo.com/computers/linu ... a-kde.html

And on Sabayon 8.0:
http://www.dedoimedo.com/computers/sabayon-8.html

I cannot find any reports of other applications then Amarok with this behavior.

Can anybody tell me where I can find a list of files that are changed/created during the first run?
The files in .kde/share/config/ and .kde/share/apps/amarok/ do not seem to have any influence on the theme-change.

amarok will likely accidentally write [Theme] instead of [Theme-amarok] in ~/.kde/share/config/plasmarc
I guess that could happen if the QApplication::applicationName() is empty what could be an issue with KUniqueApplication (but this is just a very wild guess)

Long story short:
a) try whether running "amarok --nofork" causes this as well
b) chmod -w ~/.kde/share/config/plasmarc (ensure it's not ~/.kde4/...) *might* prevent this (by locking the config against alteration. KConfig* hopefully obeys this)

plasmarc has no Theme or Theme-amarok before first run.
After that only Theme-amarok is written to the file, so there is no Theme parameter written.
Changing the desktop theme does add the Theme parameter:

[$Version]
update_info=plasma_popupapplet_fix_groups.upd:PlasmaPopupAppletFixGroups2

[Theme]
name[$d]

[Theme-amarok]
name=Amarok-Mockup

amarok --nofork results in the same behavior.
Making plasmarc read only changes the desktop theme immediately.

It seems illogical to write Amarok specific configuration to plasmarc (which causes unwanted behavior in the Plasma desktop theme) while it would be more logical to use amarokrc for Amarok specific configuration.

See also: https://bugs.kde.org/show_bug.cgi?id=163158