Red Hat Bugzilla – Bug 120228
umlauts in new qt broken
Last modified: 2007-11-30 17:10:39 EST
Description of problem:
After update the whole FC2T2 System to newest development packages,
all umlauts in KDE were replaced by some other fonts: per mille,
dots, and so on, compare screenshot.
Version-Release number of selected component (if applicable):
qt-3.3.1-0.7 brought the problem first, qt-3.3.1-0.8 has it too,
downgrade to qt-3.3.1-0.5 brings the right umlauts back.
Update FC2t2 from development tree.
Steps to Reproduce:
1. make fresh fc2t2 installation in german
2. add development tree as source into yum.conf
3. yum update
everything but the umlauts is fine
everything must be fine :)
I tried to downgrade only kdebase, or just kdelibs, but nothing
solved the problem, I had to downgrade qt.
Created attachment 99166 [details]
Screenshot of KDE with broken umlauts
Look at the window lines and at the kde boxes and the open button - in german
it must be "Ã¶ffnen".
Could you please send me your KDE default font setting? just select
Does this problem appear if you start KDE with an fresh new user?
I cannot reproduce this problem with LANG=de_DE.UTF-8
To add: I had not tried it with a fresh installation, I updatet my
system from FC2t1 to FC2t2 and then to development tree every time by
yum through internet.
So my description above maybe is not exactly how you can reproduce
My font Settings:
Allgemein/General: Sans 10
Feste Zeichenbreite/Fixed: Monospace 10
Werkzeugleiste/Toolbar: Sans 10
MenÃ¼/Menue: Sans 10
Fenstertitel/Window title: Sans 10 (bold)
Fensterleiste/Windowbar: Sans 10
ArbeitsflÃ¤che/Desktop: Sans 10
Other users: I added a user, updatet, logged in (I use KDM as
"login-manager"), and the same problems.
Than I added a second user (so the user was added after the upgrade),
and there were the same problems.
My system language: LANG=de_DE.UTF-8
strange, i have tried to reproduce this problem on many local machines
with FC2 test2, but it works fine for me.
Could you please try with a fresh installion?
Ok, I made a fresh FC2t1 install (FC2t2 seems to be impossible for me
for several reasons), and everything works normal.
So the bug was just once and is not reproduceable.