Skip to main content

NetworkManager in KDE

Many Linux distribution has been using NetworkManager as their default application to configure networking (both wired and wireless). Why don't Slackware use this as well and stick with WICD? The simple answer might be "Since it works", but the more technical answer might be "Since NM (NetworkManager) depends on GNOME packages", which is not suitable to be included in Slackware since it has abandoned GNOME since 10.2 and the work of GNOME in Slackware has been delivered by the communities.

For those who have used NM and like it very much, Eric Hameleers has given you hope by rebuilding KDE (yes, KDE only guys) package (kde-workspace) to include support for NM in form of plasmoid (KDE widget) with all the GUI networkmanagement package. Everything you need is being placed under a test directory in his KTown repository. Why test? since it's still in early testing phase, even though it's stable enough.

Please note that you need to UPGRADE kde-workspace, not INSTALL. For the rest of the packages, you can safely install them using installpkg command.

As always, you can find those packages in these repositories:

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 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 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