On Wednesday 26 November 2003 2:25 pm, James Oakley wrote:
Amazingly, it had nothing to do with the KDE updates. In the same KDE session, I updated my Gnome packages to James Ogley's releases. I thought nothing of it. Why would a Gnome package affect KDE in any way?
Indeed. Sjoerd Hiemstra posted a fix that worked for him, which was to turn off anti-aliasing in both the KDE Control Center and qtconfig. This doesn't work for me - if I have the gnome-settings-daemon running, I need to choose between anti-aliased fonts in KDE that are two sizes too big, or fonts that are the right size, but are not anti-aliased. Moreover, even though some Gnomish apps like Synaptic will respect gnome-control-center's font setting, others like GIMP don't - I presumably have to fiddle about with some other gnome1 control center for them. So I'm just putting up with crap fonts in Gnome apps. I think there is something broken in Gnome, but in a sufficiently esoteric place that it only shows up on some setups. For instance, when I opened gnome-control-center simply to do some more tests before posting this, and clicked the screensaver icon, it told me that there was no screensaver app running. This in spite of the fact that I have had Gnome random screensavers on this box for at least 3 months - the equivalent pane in KDE CC is completely empty, so that's the only place they could have come from. I didn't ask for them (although some of them are very nice), but they somehow inserted themselves as part of the install of a Gnome2 package. So how come Gnome didn't know about them? Definitely some dodgy code somewhere. -- Best wishes Kevin Donnelly www.kyfieithu.co.uk - Meddalwedd Rydd yn Gymraeg