Bug 163158

of course I meant plasma theme (lol) . 

Confirmed! This is a little but very annoying bug.

Best,
 -- Maik

Can't reproduce. What KDE version are you running as desktop?

Both Maik and I were using Arch. I am not sure about Maik, but I installed kde4 following the tutorial in the techbase : http://techbase.kde.org/Getting_Started/Build/KDE4

I can reproduce this through another way. While running kde3 in another user (kde4 is for kde-devel ), I do "su - kde-devel" and then launch amarok2 (assume .kde4 is clean). Everything fine launches like it should.

I close amarok2, start a new session/logout and login with kde-devel to kde4, and all plasma fonts are black. 

More information: Maik and I also found that Amarok2 changes .kde(4)/share/config/plasmarc .

This is a normal plasmarc file:
-------
[ViewIds]
1=1
3=2
------

After running amarok2:
-----
[Theme]
name=Amarok-Mockup

[ViewIds]
1=-1238895848
3=2
---------

The problem comes from (I believe), 1=<random huge number here>, with Maik it resulted in a large positive, with me it's usually negative, right now I just got a new one:
[ViewIds]
1=-1239411944

By erasing plasmarc, everything is ok. Until we run amarok2 again.

ViewIds is NOT the cause of this bug afaik.

It is:
[Theme]
name=Amarok-Mockup

this sets the plasma theme to Amarok-Mockup, which doesn't exist for plasma.

If you look in Desktop Settings, the theme is actually blank, setting the theme back to default or another theme will fix the black fonts issue.

I'm not sure if this bug is in libplasma or amarok.

It's fixed :)

< CIA-38> nhnielsen * r819922 amarok/trunk/extragear/multimedia/amarok/src/context/ContextScene.cpp:
Fix Amarok's nasty evil habbit of overwriting plasmarc. This should make a lot of people happy, myself included! :-) Thanks to Alessandro Diaferia for pointing us in the right direction!

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

KDE: 4.7.4
Amarok: 2.5

This is also 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 solved this by creating a plasmarc in the skel directory.


mkdir -p /etc/skel/.kde/share/config
echo "[$Version]" > /etc/skel/.kde/share/config/plasmarc
echo "update_info=plasma_popupapplet_fix_groups.upd:PlasmaPopupAppletFixGroups2" >> /etc/skel/.kde/share/config/plasmarc
echo "" >> /etc/skel/.kde/share/config/plasmarc
echo "[Theme]" >> /etc/skel/.kde/share/config/plasmarc
echo "name[$d]" >> /etc/skel/.kde/share/config/plasmarc
echo "" >> /etc/skel/.kde/share/config/plasmarc
echo "[Theme-amarok]" >> /etc/skel/.kde/share/config/plasmarc
echo "name=Amarok-Mockup" >> /etc/skel/.kde/share/config/plasmarc

(In reply to comment #7)
> I regretfully must confirm this issue.
> Working on a Debian based distribution with KDE, I can reproduce this for
> every first run of Amarok.
> 
> KDE: 4.7.4
> Amarok: 2.5
> 
> This is also 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

You are kidding, and nobody reported this upstream since 2008? Very annoying

Can somebody confirm this, please?

The same when pointing to debian testing:
KDE 4.8 
Amarok 2.5

One of the above mentioned links went wrong:
http://www.dedoimedo.com/computers/linux-mint-lisa-kde.html

Paragraph: Problems (at the bottom, just above Conclusion).

I use a Debian based distribution, Kubuntu 12.04 and current Amarok 2.5-git. I have never seen that happen nor did I see that reported by somebody else. I strongly suspect a distribution specific problem.
FWIW: Sabayon is NOT Debian but Gentoo based...

Also, if I ask if somebody else can confirm that this was not about blog posts for the same distro, but actuall different users on same/different distributions.

Correct, Kubuntu does not suffer from this issue. No plasmarc is created but in Debian with KDE if no plasmarc is present, Amarok creates it with the following content:

[Theme-amarok]
name=Amarok-Mockup

The plasma desktop then defaults to the oxygen theme and every time this parameter is removed, Amarok put it back again and defaults back to the oxygen theme.

Adding
[Theme]
name[$d]
to plasmarc suffices to return to the theme you began with (in my case the Air theme).

This to me does not sound like a distribution specific problem because it's Amarok that generates or adepts plasmarc. It is also the only application so far with this particular issue.

This issue was also reported on May 25th on the KDE forum: http://forum.kde.org/viewtopic.php?f=111&t=101895

Now, I personally have a workaround as I stated above, but I'm just trying to help the developers to make their product better.

(In reply to comment #13)
> Correct, Kubuntu does not suffer from this issue. No plasmarc is created but
> in Debian with KDE if no plasmarc is present, Amarok creates it with the
...

See, that is where the problem starts: the plasmarc is created on first KDE start as Plasma is the default desktop in KDE. If that doesn't happen then something is wrong in your installation, Amarok only creates it if it is not present, but again, that would only happen if you run it in a non-KDE desktop. 

So a Debian with KDE needs to have a plasmarc created by Plasma, everything else is a bug and certainly a distribution related one, as KDE by default should always have a plasmarc created on KDE startup.

Closing as downstream, please report this to your distribution.