Anyway... I "distro-hopped" a lot in those past years. Debian, Ubuntu, Kubuntu, Xubuntu, Lubuntu, OpenSUSE, CentOS, back to Ubuntu ... then I found "Zorin OS". And then I needed to replace my old broken Nvidia card with a new one ... and this is where my frustrations began. Thanks to some weird combination of kernel bug, 'nouveau' not supporting this new graphics card yet and the proprietary Nvidia driver and the kernel not getting along I experienced soooo many system freezes and crashes ... :/
One of my coworkers recommended I try this distro he had "run into": Linux Mint.
But OK... why not? It's been a loooooong time so why not try it again?
Oh man, I *really* love what I see here!!
You guys can safely assume I'm still the undiplomatic brutally direct guy I was in 'the old days'... so me making a compliment means I really do mean it. (I don't dish out compliments lightly... )
Stability problems: gone. This OS just works, it's full of polish, bells and whistles, offers plenty of customisation features.... Awwwww, wonderful
The only major bug I've found is the one which all Ubuntu-based distros have since Ubuntu 15.04: "systemd" prevents eCryptFS-encrypted home directories from properly being unmounted ...
The result is that even when you log out, your home directory stays open! e.g. anyone having any other account on the system can still read the contents of your home folder, especially if they have access to the "root" account, either directly or via "su" or "sudo". The expected behaviour would be that once you log off your home folder goes back into its encrypted state .... but nope!! This bug is preventing it. On a desktop system this might not be a big deal ... but on a laptop this means your files could be accessed + stolen if anyone can get their hands on your device.
Create a "cron" job for super-user "root" that runs once every minute and which will try to unmount your eCryptFS-encrypted home directory. If you're still logged in nothing will happen as the binary will run into a "device busy" error (which is silently discarded with the help of 'pipes' so log files etc. don't get filled up with redundant messages). If however you happen to be logged out in that moment the home directory will return to its encrypted state, e.g. we get the desired result again.
Launch the 'crontab' editor as super-user "root":
Code: Select all
sudo crontab -e
Code: Select all
*/1 * * * * /sbin/umount.ecryptfs /home/YOURUSERNAMEHERE > /dev/null 2>&1
So until Canonical and/or the people around "systemd" finally fix this stupid bug this little workaround above should do the trick.