Qt 4.7.0 and KDE 4.5.2 - Yay!

Message

vdracula · Post by **vdracula** » Wed Nov 10, 2010 2:54 pm

Bug was filed

http://bugs.gentoo.org/show_bug.cgi?id=344933

Martux · Post by **Martux** » Wed Nov 10, 2010 5:32 pm

@KejPi:
QtCurve, it's possible, I also use it here.
Problem still persists with QT-4.7.1.

vdracula · Post by **vdracula** » Wed Nov 10, 2010 8:11 pm

Changing to oxygen and cleaning out kdecache and sockets in /tmp and /var/tmp helped.

Do not see any crashes since.

KejPi · Post by **KejPi** » Fri Nov 12, 2010 5:47 pm

In my case this has been confirmed as a bug in QtCurve related to raster graphics system in QT - http://kde-look.org/content/show.php?co ... umpage=140

Martux · Post by **Martux** » Wed Nov 17, 2010 7:28 pm

It seems to be the QT raster bug for me too. Updating qtcurve to 1.7.2 fixed the problem partly.
Now only kde4-windows-decorator is crashing @logout...

KejPi · Post by **KejPi** » Wed Nov 17, 2010 7:30 pm

Seems to me there is a lot of problems with Qt 4.7 and KDE 4.5. I solved it by downgrade of Qt bask to 4.6 which was painful but worth to do it

reup · Post by **reup** » Sat Nov 20, 2010 1:35 am

a quick question please, did you have to remove kde 4.4.x before upgrading to kde 4.5.x ? I encounter a lot of block packages when trying to upgrade

Shining Arcanine · Post by **Shining Arcanine** » Sat Nov 20, 2010 3:50 am

reup wrote:a quick question please, did you have to remove kde 4.4.x before upgrading to kde 4.5.x ? I encounter a lot of block packages when trying to upgrade

I did not have to remove it, although a few things I installed in a local overlay had to be uninstalled first.

reup · Post by **reup** » Sat Nov 20, 2010 1:52 pm

thanks.

view to other post, I think I will hold on to 4.4 until 4.6 anyway. this is my production station, dont want to mess it up

Shining Arcanine · Post by **Shining Arcanine** » Sat Nov 20, 2010 3:52 pm

reup wrote:thanks.

view to other post, I think I will hold on to 4.4 until 4.6 anyway. this is my production station, dont want to mess it up

There will always be blockers, but portage should be able to resolve them. The things I had to remove were things like kwebkit-part and knetworkmanager, which were proposed ebuilds for parts of KDE that had not yet been in portage at the time of KDE 4.4.x. Versions compatible with KDE 4.5.x are in the portage tree now, so having installed the experimental ebuilds from the bug tracker in a local overlay no longer makes sense.

You will likely need to leave your system compiling for a night, but the upgrade should not be anymore painful than the upgrade to KDE 4.4.x. Any real blockers that prevent portage from upgrading will likely be mentioned before portage will proceed, such as the kwebkit-part ebuild I had in a local overlay.

At the same time, KDE 4.6.0 is two months away from release, so if you upgrade now, you could be upgrading again in two months.