Flatpak is not that bad ...

... for desktop applications.

I'm running openSuse LEAP on my workstation and sometimes I have to struggle to get recent versions of some program to work. Recently I had to fight with two applications, with only minor success: Steam and GIMP.
Probably I'm not the only one who occasionally find itself trapped in a dilemma here. It's a clash of two different philosophies: On one hand on my workstation I want to have a rather stable distribution (thus LEAP, on my Laptop I run Tumbleweed), on the other hand I'm using certain programs, that only come in outdated packages (Gimp 2.8!!1!) or have some issues with outdated libraries ecc. e.g. Steam works nicely with some games, others like Civilization Beyond Earth do not work at all.


Flatpak solves this issue here: It delivers a piece of software including all dependencies and stuff. It's thus able to decouple a single program from the system dependencies. This solved the above mentioned clash: The bare system can be a rather conservative and stable one, and you still can run a very recent version of your program, without going through the nightmare of a dependency hell.

Gimp 2.10 for instance can be installed in two lines and just works, whereas I spend an awful lot of time to get it running as native application with unsolvable dependency conflicts at the end. It was running some time ago, but then for some reason it broke. That's not what stable is about.

That one installs it and it just runs. And that's pretty neat.

Urgent: Nextcry ransomware

A recently disocever bug, CVE-2019-11043 opens the door for a newly identified ransomware named "Nextcry". If you configured your Nextcloud to run on nginx as reverse proxy (as I have done) you could be affected. Update php-fpm NOW.


On this Nextcloud page you find instructions how to mitigate the issue. I post it here as personal mirror

You need two changes in your nginx.conf:



Becomes (Add $try_files $fastcgi_script_name =404;)

Here I post my configuration, that is slightly modified as I run currently on FreeBSD.


And a kind reminder, that the only viable protection against Ransomware are occurring offline backups on separate media. I burn my backups still on Blue-Rays, as this is the only fool-proof way of protecting your data against software threads like Ransomware or stupid user errors.

Sourdough - Day 4

After another 24h both glasses are already raising. The sourdough started is now active and can be used for baking. I'll still feed them and let them stand for another day, but in principle this is how it should look and what you need to do.

Finished sourdough in jam glasses. Left: Rye based, Right: Wheat/Spelt based

Sourdough in about 4-5 days from scratch, using nothing but flour and water. Nature provides really everything you can wish for 🙂

Sourdough - day 3

After another day, the sourdough should be already pretty active. A slight soury smell and visible bubbles are arising. This shows us, the bacteria are active and doing exactly what they are supposed to be doing.

Bubbles and a mild sour smell. That's how it should be!

Until now I made a very generic sourdough. Now it's time for the dough to specialise. With specilise I mean, that we create trunks for the different flour types we intent to use. I mostly bake with wheat/spelt and with rye, so I'm gonna create two types of sourdough.

Ultimately I want to have two different jam glasses in the fridge, one for wheat/spelt and one for rye. In general sourdough likes it to always have the same kind of flour and because wheat, spelt and rye are different grains it's recommended to have different sourdough for each of them. I mix spelt and wheat together, because until now I had good results with this combination.

So, I take now two jam glasses, fill them 1/4 with flour and add 4 tablespoons of our sourdough to each of them. Then I mix the contents and add warm water until we reach a very liquid, but sill doughy consistence. This we now let raise for another day.

Left is the rye-based sourdough, right is the wheat/spelt based sourdough. They are now going to raise for 12h

In about 12h we're probably have to feed them again. Now the activity of the sourdough should be already pretty good.

Sourdough - day 2

Day two of making sourdough from scratch. The dough starts to have some larger bubbles and already smells mildly sour. Looks good so far!

This is how your sourdough should look after 1-2 days. Some larger bubbles form as result of the process the bacteria are doing in the dough

I removed more than half of the dough and fed the remains with fresh flour and water. After re-feeding all of the bubbles are gone. After some minutes some small new bubbles start to form. This is a good sign for activity and shows us, that we are on the right way. Actually a bit faster than I though 🙂

Looks like we're soon ready to make new bread again 🙂

Sourdough - Day 1

Just a tiny update on the sourdough process. After 1 day some small bubbles start to form. I've fed the dough using again 50g flour and 50g water. On day 1 I don't remove old dough, as I think the number of absolute bacteria is still low and needs to be increased first.

Developing sourdough, already has some small bubbles after 1 day

We're having about 19 degrees here in the house. It's not optimal but it seems to work. Could be that it's slowed down a little bit because of the temperature. Anyways, the bacteria are pretty resilient, so no need to worry. Might just take a day longer 😉

Sourdough starter

Sourdough from Scratch

I'm starting a new sourdough culture from scratch. All you need is flour, water a nice and warm spot and some time.


  • 50g wholemeal flour
  • 50g universal flour
  • ca. 50-100g water

Mix everything nicely together and put to rest for a day. The bacteria prefer temperature between 20 and 25 degrees. Low temperature encourage lactate-bacteria growth (sour taste), higher temperature yeast bacteria. In the end you want to have both, so keeping the temperature in this range is recommended.

Also making sourdough and bread from it is one of the crucial skills everyone should know for the unavoidable upcoming zombie apocalypse 😉

Windows 10 Clock in UTC

If you are running Windows and Linux in dual boot, you will soon find out, that the clocks are not matching. Most probable the reason is that Windows by default expects the computer time to be set to local time, while Linux assumes it to be UTC.

I consider the approach of Linux the better one: The BIOS/UEFI system time is there set to a global harmonised standard, UTC. The operating system then translates this to the local time. This means you can install as many operating systems in parallel without interference of them with the system time - just immagine if you have for example, Windows, FreeBSD and two Linux distributions on your computer and every one of them wants to account for daylight saving time .... When setting the system clock to UTC, this problem will never arise.

Setting Windows to use UTC as system time

Registry magic! Create a new registry key named RealTimeIsUniversal.reg with the following contents.

Alternatively you can create a QWORD (or DWORD for 32-bit Windows) with the value "1" in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal

Then reboot Windows and set the time zone to UTC

If unsure, try another reboot to check if the settings persists, but that should do the job.