Systemd

This setup is a hands-free way to keep your Flatpak applications updated automatically. With the timer and service file, you don’t have to worry about manually checking for updates, as everything is done for you at regular intervals. Timer Unit: tolga.timer Create file: sudo nano ~/.config/systemd/user/tolga.timer [Unit] Description=Run Tolga's Service Every 5 Minutes VER:2.0A [Timer] OnBootSec=1min OnUnitActiveSec=5min Unit=tolga.service [Install] WantedBy=timers.target This timer is responsible for triggering the service that handles Flatpak updates. ...

The Fuckup I wanted to migrate from Hugo to WordPress. Seemed simple. It wasn’t. I spent hours trying to install WordPress on my T620 thin client. Each time I “fixed” it, something else broke. By the end, both WordPress AND my Hugo site were completely fucked. Nginx wouldn’t start. The main blog was down. I had wasted hours on something that should have taken 30 minutes. Then I remembered: I had full backups. ...

I spent the last month building what should have been a simple update checker for my G4 Fedora 44 box. Turned into a proper rabbit hole once I discovered the system was hanging after three days of suspend. Here’s what I learned. The Problem I run a lot of machines. Rather than babysitting each one for updates, I wanted something like CachyOS has: a tray icon that checks hourly, shows a green dot when up to date, red when updates are pending, and handles the background automation so I never have to think about it. ...

Most people manually update stuff when they remember. But you can make your system do it automatically with a couple of files. I was looking at keeping on top of flatpak, snap, and appimage updates and realised I just forget to do it. Found this solution using systemd timers, pretty straightforward. What we’re building Two files that work together: A bash script that runs the actual updates A systemd timer that says when to run it That’s it. No daemons running constantly, no cron job headaches, just systemd doing what it’s built for. ...

Reboot the system. It hangs. Doesn’t crash, doesn’t give an error on screen, just sits there for what feels like forever. Eventually it times out and reboots anyway. But every single reboot does this. Check the logs and you see this: plasma-plasmashell.service: State 'stop-sigterm' timed out. Aborting. plasma-plasmashell.service: Failed with result 'timeout'. KDE Plasma is not shutting down in time. The system gives it a timeout to close gracefully, and Plasma needs more time than that timeout allows. ...

Started with something dumb. Facebook wouldn’t load in Vivaldi or Firefox on the desktop. Worked fine on mobile. Figured it was a browser thing at first. Extension, cookies, the usual 💨 . Wasn’t that. why i thought i might need ipv6 Ran a curl test forcing each protocol separately, just to rule stuff in or out: curl -4 -I https://www.facebook.com curl -6 -I https://www.facebook.com IPv4 came back clean. HTTP/2 200, instant. IPv6 flat out refused to connect: ...

The problem this actually solves On a normal distro, if a network mount goes stale … the connection dropped, the server bounced, whatever … the fix is usually sudo umount then sudo mount -a, reading straight from /etc/fstab. Simple, because fstab is a plain text file you can just point tools at. NixOS doesn’t work that way. fileSystems entries in configuration.nix get compiled into individual systemd .mount units automatically at build time. There’s no /etc/fstab to edit or run mount -a against in the traditional sense … the mounts exist purely as generated systemd units with names like mnt-t620\x2drelationships.mount. ...

The actual bug WPS Office’s flatpak ships a background helper called wpscloudsvr that reliably segfaults … null-pointer deref inside libqingbangong.so, r15=0x0, the works. Not a config issue, not something I broke, just a genuinely broken binary shipped in the package. It doesn’t crash the whole app, just spams crash reports and burns CPU respawning itself. The fix nobody’s going to like, but it works You can’t easily patch a binary inside a flatpak sandbox, and there’s no config flag to just disable this one helper. So: bind-mount /dev/null directly over the broken executable. The file still “exists” as far as the OS is concerned, it just contains nothing … attempting to execute it does nothing, silently, forever. ...