Skip to main content

Finally, a Working KDE 4.11

I have been trying to use KDE 4.11 twice. My first attempt was 4.11 RC1 and it failed miserably since KWin keep crashing on my desktop so i had to postponed of testing it further. My second attempt was 4.11 Final and again, it failed due to the same reason. After that i gave up and downgraded to KDE 4.10.5 which was rock solid and stable.

I discussed this matter with Walecha and some other Slackware user in AlienBOB's blog post about KDE 4.11 and we thought that it might be Qt who need to be upgraded to 4.8.5 so that it should work fine. So i pulled Qt 4.8.5 and adjust Slackware's Qt SlackBuild (since there are two patches that are already part of Qt 4.8.5, so no longer needed) and build the package by myself.

After upgrading Qt, i continue by upgrading to KDE 4.11 and reboot my system. I logged in to my desktop and surprisingly, no more crashes here. It's still less than 24 hours, but i hope this will work in the future as well.

So, for those who wanted to try KDE 4.11 and having a crashed KWin all the time, please try to build Qt 4.8.5 and upgrade it before installing KDE 4.11. Don't forget to make a backup copy of your .kde directory under your home directory just to be safe. You can delete it later when you have make sure that KDE 4.11 is working on your system.

After this, i will need to rebuild digiKam since KDE libraries has changed, but i will not rebuild amarok as Eric has stated that amaroK 2.8 will be pushed to -Current on the next batch of update. I can live with 2.7 for few days.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue