[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Update 2.2.1 -> 2.2.2 -> weird behavior



Next part of my "monologue":

I wrote:
> 1) Sound server does not start, even though it is properly configured.

Not correct. Sound server does start, but is/was muted. After "Load
volumes" under Sound -> Mixer sound plays.

For some reason this works now. It seems that "Load volumes on login"
had no effect...

> > 2) Fonts for non-KDE apps:
> > 
> > I use Opera. "General font" is set to verdana/8 under Look & Feel ->
> > Fonts. AA is on and working correctly. 
>
> Correction: The font is NOT aa'd, neither does Opera (dynamically linked
> to qt; using qt 2.3.1-16) display any aa'd fonts in browser window
> _at_all_.

> I set QT_XFT to 1 in /etc/environment. Now Opera does display AA'd fonts
> in browser but still uses an ugly big font for its interface.

Could work around the problem by selecting my favourite font within
Opera. This does, however, still leave the question why "General font"
under KDE did not apply to a non-KDE but yes-QT application....? (like
under 2.2.1)

> 3) Battery Monitor does not show up automatically on starting KDE.

Erm... my mistake... sort of: I found some old crypto packages
(kdelibs3-crypto and kdebase-crypto) from 2.2.1 on my system. After
removing them, battery monitor comes up again. (Why?) Maybe a "conflict"
tag would do to avoid this...?

Thomas

-- 
Thomas Winischhofer
Vienna/Austria                  Check it out:
mailto:tw@webit.com              http://www.webit.com/tw



Reply to: