Skip to main content

Facebook Export on Digikam 2.0

One of the feature i like from digiKam is it's ability to export to Facebook directly thanks to Kipi-Plugins. I don't have to upload them one by one, but i can do bulk upload and leave them uploading while i'm sleeping.

On digiKam 2.0.0 release, Kipi-Plugins are now being included in the digiKam 2.0.0 source, so there's no need to compile two packages anymore. Today, i checked my digiKam 2.0.0 and see if there's new plugins, but i realized that Export to Facebook menu is no longer exist. Then i checked digiKam README but found no information about it. Next, i checked Kipi-Plugins README and i found out that i need qjson as the requirement to Export to Facebook.

In the end, i have to recompile digiKam after installing qjson (thanks to SlackBuilds) in order to recognize the library and thus it enables Export to Facebook plugin again Yahoo

So if you decided to upgrade to digiKam 2.0.0 and above, please have a look on both README (mostly the Kipi-Plugin README) to make sure your previous Kipi-Plugins dependencies has been met to save your time recompiling digiKam.

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