x11-libs/qt-4.3.4-r1 which included the change append-flags -fno-strict-aliasing ie bug 213411 seems to cause this problem in KDE 4.0.2. http://bugs.kde.org/show_bug.cgi?id=158409 A screen shot is attached to the KDE bug, it was recommended I create a bug here outlining the problem. I think this is fixed in KDE SVN but I'm not sure. Reproducible: Always Steps to Reproduce: 1. Upgrade to x11-libs/qt-4.3.4-r1 2. Run KDE 4.0.2, notice calendar 3. Downgrade to x11-libs/qt-4.3.4 problem goes away 4. Upgrade to x11-libs/qt-4.3.4-r1 problem returns.
From that KDE bug: ------- Additional Comment #20 From David 2008-03-21 18:53 ------- .... I had this problem with Qt-copy 4.4.0 from kde's svn too! Huh? After qt-4.3.4-r1 upgrade, did you recompile any kde package? I do not know how far kde is chained with qt but that change in qt revision could require a recompile of (parts of) kde.
(In reply to comment #1) > I do not know how far kde is chained with qt but that change in qt revision > could require a recompile of (parts of) kde. Recompiling kdelibs should do. These anti-aliasing problems are fixed in Qt-4.4.0 pre-releases iirc.
I re-compiled kdelibs-4.0.2 didn't fix it. I'd rather not use qt-4.4.0 betas if I can help it. Currently using qt-4.3.4-r1 (revdep-rebuild didn't request to rebuild kdelibs so i had to manually --oneshot remerge it)
This has been resolved upstream.
