I just recompiled kdm as it didn't work...
I did not know there were kdm-related problems, before i stumbled over them by myself.
(But I don't want to give away qt-4.5... It's -- whooo, fast and less glitches )

Did you remerge at least kdelibs after upgrading Qt (as suggested by elog message)?

hi. i used qt-4.5 from 4.1.8x to 4.1.96, but i switched back to qt 4.4 with the stable release of 4.2.

in short. yes, i rebuild kdelibs.
--
for 4.2 release of kde, i removed every set from portage and did a depclean, then i build kde 4.2 from scratch including all dependencies. maybe the problem would have been resolved if i did this with qt-4.5 too ...

Well Qt4.5 will be out before kde 4.3 will wont it, so that patch will have to be backported? I dont see why fixes like that wont make it into the main tree if they'll be needed when Qt4.5 goes stable anyway.

Well Qt4.5 will be out before kde 4.3 will wont it, so that patch will have to be backported? I dont see why fixes like that wont make it into the main tree if they'll be needed when Qt4.5 goes stable anyway.

Erm, read EXACTLY what the page says
It's a backport-fix from kde-trunk, it is just in the 4.2-branch. So kde-4.2.1 will contain this fix!
It should even be possible, to add this patch to kdm in portage.

Well Qt4.5 will be out before kde 4.3 will wont it, so that patch will have to be backported? I dont see why fixes like that wont make it into the main tree if they'll be needed when Qt4.5 goes stable anyway.

Erm, read EXACTLY what the page says
It's a backport-fix from kde-trunk, it is just in the 4.2-branch. So kde-4.2.1 will contain this fix!
It should even be possible, to add this patch to kdm in portage.

yeah, my point was I dont think it'll be a problem for long, as it could be added to kdm-4.2.0-r1 in portage.

I'm having very good results on three different boxes with qt-4.5-rc1, and kde-live- no problems so far.
Correct me if I'm wrong, but I've always found far less problems using the very latest qt release (rcx's included, but NOT qt-live revisions) and then building kde-live (9999) versions on that.

The other way, i.e. trying to build newer revisions of qt on an earlier kde is far more problematic (even if you rebuild the given kde version afterwards), and for me at least (in compiling time) is not worth the effort.

IMHO, if you are wanting to use qt-live 9999's, then also using kde-live would be almost mandatory to avoid lots of problems, as qt-live is going to be moving past (for example) kde-4.2.0 or any "point" release, almost immediately. In other words, a qt-4.5-rcx is more likely to be OK for a good many kde-live 9999 rebuilds than a kde-4.2.0 release is for the ongoing qt 9999's._________________Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.26-r5, gcc-7.3.0 kernel-4.15.7-gentoo USE=experimental

works with qt-4.5-rc1 and kde-live (don't know about any other versions). As a test, I just burnt the newest SystemRescue iso, and k3b worked normally, no problems. First time I've ever been able to get k3b to work with kde4 (any version).

:/, pretty terrible if you ask me, I need qt4.5 for other things that kde (I'm a developer using qt activly), and not having it is unpractical. It wont stop me from using 4.5 ofc, I'll just kill off whatever plasmoids doesn't work, but it still sucks.