All Cyanogenmod 13 nightly builds past July 28 seem to be affected by a bug that makes the phone reboot just a few seconds after opening the Gallery application. The issue seems to be related to the newly added support to sdcardfs which obviously isn’t playing well at the moment. A workaround to prevent the phone from crashing and rebooting is to edit the build.prop file located in /system; this can be done either via adb using the command adb shell or more practically directly on the phone using the built in file manager and text editor (provided that in file manager’s settings access mode option is set to Root access mode).

RawTherapee from my experience is by far the best program to manipulate RAF files, it’s demosaic algorithm for Fujifilm X-Trans sensors is astonishingly good. Too bad that, like for Darktable, the version included in Fedora’s repos is outdated to say the least. To install from source first install some dependecies: $ sudo dnf install bzip2-devel cmake exiv2-devel expat-devel fftw-devel gcc-c++ glib2-devel glibmm24-devel gtk3-devel gtkmm30-devel lcms2-devel libcanberra-devel libiptcdata-devel libjpeg-turbo-devel libpng-devel libsigc++20-devel libtiff-devel zlib-devel gtkmm24-devel lensfun-devel Git clone and install …

Darktable documentation on this matter is somewhat fragmented, so I figure a small how-to on how to install it from source on Fedora 23 could be useful. The version included in the official repositories is really old (version 1.6.9 as per today) and is missing some important presets for many widely used cameras. The latest version source code archive can be downloaded from here: https://github.com/darktable-org/darktable/releases. Before compiling and installing the software the following dependencies must be installed: …

CentOS repos (both official and EPEL) does not provide an up to date version of Ejabberd, installing from source is the only way if one want or need a version from this century. Problem is that doing things manually is a never ever a good idea, luckily Ansible and a bit of Python love come to rescue. Supposing Ejabberd is already installed and configured (I wrote a post on the subject a couple of years ago: https://nagg.eu/ejabberd-xmpp-server-configuration-guide//) the following Ansible script will take care of all the steps needed to upgrade to a newer version of Ejabberd …

Android ROM scene is cluster fuck of inhumane proportion; the complete lack of documentation, decent how-to, decent guides and the retarded works for me attitude the whole community has really amazes me. TWRP project is a good example of a really useful tool used by [millions] of people all over the world, one would assume that it has to be maintained in a professional way but this is as far from the reality as something can get. The official site lacks any kind of documentation, the only information one can find there are either completely useless or partial and incomplete (e.g. the how to build from source guide linked on TWRP faq page is a link to a XDA forum post saying absolutely nothing on how to build this shit). Not only that, but the site download page (one would hope that at least that part was taken care of…) is not up to date. For bacon (oneplus one), which is a really popular phone among modders, the latest version present in the download page of the official TWRP site is the buggy and completely useless twrp-2.8.7.0-bacon. To get the latest version (twrp-2.8.7.1-bacon) which supports file-system encryption on CM13 and correctly flash the baseband ROM one has to dig through a whole pile of shit on XDA and finally find a post where pajeet post a link where to download it: http://build.twrp.me/twrp/twrp-2.8.7.1-bacon.img The irony is that the link is from the TWRP official site even though it can’t be found anywhere on the bacon download page on the very same site. In case someone decide to delete the file I am rehosting it here: https://nagg.eu/misc/twrp-2.8.7.1-bacon.img …

Every time I have to setup a software RAID in Linux using mdadm I forget something, this time I am writing it down once and for all (or at least I hope so). For the sake of simplicity I will use the creation of a RAID1 as example but this very same procedure can be applied for any other kind of RAID. RAID array creation 1. Partition the drives This step must be repeated for each drive of the array (/dev/sdb and /dev/sdc in my case). …

XFS just like EXT4 (I wrote a post about it last year) supports online defragmentation, to manage those volumes on CentOS and Fedora xfsprogs package is needed. Fragmentation level of XFS volumes can be checked with the command: [root@CentOS ~]$ xfs_db -c frag -r /dev/sdb1 actual 4491, ideal 4006, fragmentation factor 10.80% To perform online defragmentation of XFS volumes run the following command: …

After some time qcow2 images tend -especially after taking snapshots- to grow bigger and bigger, even bigger than the maximum size specified at creation time. QEMU provides a tool called virt-sparsify (install libguestfs-tools package in CentOS 7) that can effectively make a virtual machine disk thin provisioned (space is not preallocated, only the actual space needed is used). virt-sparsify has a nice number of options, the most interesting one is --in-place, it tells QEMU to shrink the volume in place without requiring any addition space. …

DNSCrypt installation process is pretty simple since it is present in the repository, pdnsd on the other hand is missing, luckily compiling from source is not that hard. For the sake of completeness I will also cover the procedure to install DNSCrypt from source, alternatively yum install dnscrypt-proxy. Install the required dependencies and get the source code: [root@CentOS ~]# yum install gcc libsodium-devel libtool-ltdl-dev git wget [root@CentOS ~]# git clone https://github.com/jedisct1/dnscrypt-proxy.git [root@CentOS ~]# wget http://members.home.nl/p.a.rombouts/pdnsd/releases/pdnsd-1.2.9a-par.tar.gz pdnsd Compile and install: …

Since every time I am about to install Vim I forgot how to set it up, set it as default system wide text editor and so on I figure I’ll write it down once and for all. First of all let’s install Vim, specifically the so called enhanced version which is capable of loading plugins and colorschemes: [user@Fedora ~]# sudo dnf install vim ### powerline plugin [user@Fedora ~]# sudo dnf install vim-plugin-powerline I personally really like molokay colorscheme from tomasr; putting it in the default colorscheme directory does the trick if we want to use it for every user. …