Skip to main content

MATE 1.6 For Slackware-Current (14.1)

As Slackware 14.1 is getting closer to gets released by Patrick, i'm also preparing a binary packages for the upcoming Slackware 14.1. We (me and Chess) have been discussing about our roadmap for MATE and since MATE 1.8 will not be available before Slackware 14.1 gets released, we will provide MATE 1.6 for Slackware 14.1 for now.

We have arranged a new git branch called current-mate-1.6 in our GIT repo that will serve as the base for building binary packages for Slackware-Current until Slackware 14.1 gets finalized. When it's released, we will rename the git branch into 14.1-mate-1.6 and this will be the new stable branch that are officially supported by us.

What will happen with the "1.6" git branch? We will rename it into 14.0-mate-1.6 (to be consistent) and we will leave it as it is. You are free to checkout this branch and use it to update your MATE packages if you are still running Slackware 14.0, but no binary packages will be provided once Slackware 14.1 gets released. You can still build your MATE packages from this branch.

When MATE 1.8 gets released (probably next year), we will move on to support MATE 1.8 on Slackware 14.1 (or 14.2 or 15.0 when it's released) and a new branch will be made for that purpose.

Speaking about MATE 1.6 for Slackware-Current (14.1), i have tested here with virtual machines on both arch (32/64 bit) and they are working fine as expected. They are the latest Slackware-Current updates per 25 September 2013. The number of packages included in MSB has been reduced since there was some packages that are now included in the default Slackware installation.

For those running -Current, you can also try this version by checking out the current-mate-1.6 branch and start building MATE packages.

Here are some screenshots of MATE 1.6 running on 32 bit (above) and 64 bit (below).

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