Skip to main content

KDE 4.4.2 With PolicyKit From Eric

For some time, people may be wondering, why on earth Slackware-Current hasn't include KDE 4.4 on the tree even though it has released their second maintenance version (4.4.2). Well, Eric or most people know him as AlienBOB has described the problem on LQ.

In short, Slackware is not able to satisfy some of the requirements that KDE 4.4.x depends on, which is PolicyKit. Why is that? Because PolicyKit depends on PAM, something that makes GNOME were not being distributed again in Slackware since 10.2 since it requires PAM. This resulted in two options: leave KDE 4.4 (or probably abandon KDE like GNOME if no further action can be done with KDE) or wait until PolicyKit is able to be built without being dependend to PAM. That's why Pat still uses KDE 4.3.x in -Current and probably add KDE 4.4 or 4.5 when the next next Slackware release, yes, it's a double next (14 or 13.2).

The long await has finally paid off. Piter PUNK and Robby Workman has worked with one of the WICD developer to make PolicyKit buildable without PAM. The real output of this work is the new shinny KDE 4.4.2 on Eric's repository which already include PolicyKit that is build without PAM.

I'm not sure whether this work can be included in the -Current or not, but i do believe that most people who used KDE will be happy to see this work, as KDE without PolicyKit will loss some of it's functionality, such as updating the time, install new fonts and printers. Right now, the problem is fixed, but don't expect to see them in the official -Current tree in short time Goodluck

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