Bug 600945

Don't assume that it is the same for everybody. It is not reproducible here with GNOME, Fedora 13, x86_64.

Some investigation is needed, please:

 - Can you reproduce it with a fresh user account?

 - Can you save and attach a copy of your $HOME/.config/audacious/config file?

Created attachment 421642 [details]
Audacious config file

Audacious config.

Okay, it works with a newly created user.  Attached config from broken user, but no different than working user.

I figured out the problem:
In my .config/kde.org/systemsettings.conf file I have:
[qt]
font="Sans Serif,10,-1,5,50,0,0,0,0,0"

I'm not sure how that got set, but this is what is causing the fonts to not show up in the audacious menus for me.

Okay, this configuration setting is written when you access the "System Settings" dialog box and select Appearance -> Fonts and then change a font (I changed Window title to be italic or bold italic).

Created attachment 421745 [details]
screen snapshot (KDE)

With a fresh install of F13 KDE x86_64 and default KDE settings, Audacious starts with dark-grey fonts, which are hardly readable. See comment 6 attachment.

> System Settings > Appearance > Fonts

Here I don't need to change anything. It is sufficient to click something and revert it again, then click the "Apply" button which gets enabled by that action.
Immediately afterwards, the fonts/dialogs in a restarted Audacious become readable until next reboot.

My post to Fedora's KDE list has not been responded to:
http://lists.fedoraproject.org/pipermail/kde/2010-June/007281.html

I can confirm some odd behavior alright, before and after tweaking systemsettings' font configs.  I'm more than a little baffled, esp after trying manually adjusting ~/.gtkrc-2.0-kde4

Thanks, Rex!   IMO, it's not anything like important, considering that it has never been reported before and isn't anything like a most-popular bug. Also, Audacious 2.4 in Fedora 14 features an alternative non-skinned GTK+ interface.

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.