Linux

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. ...

Why This Script Exists Every time I write a new blog post, Hugo has to rebuild the entire site. That means recompiling all the markdown, regenerating all the HTML, copying files to the web root where nginx can serve them, and fixing Linux file permissions so nginx can actually read them. Doing all that manually is tedious. Running separate commands every time is error-prone. I wanted one command that does everything. ...

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. ...

Every time a new kernel arrives via dnf upgrade, your Fedora EFI boot entry disappears. You reboot and the UEFI firmware can’t find Fedora anymore. You have to manually regenerate GRUB and recreate the boot entry. Again. This is a Fedora issue with duplicate or malformed boot entries in the UEFI firmware. The kernel update process has hooks that regenerate GRUB, but if you have bad entries sitting there, the system gets confused and deletes the good one instead of refreshing it. ...

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. ...

I run a QNAP TS-459 Pro+ as my homelab NAS, connected to several Linux machines across different distros. Fedora 44, NixOS, Solus, whatever. The problem: I had to remember different commands to check disk status, restart NFS, fix permissions, manage keepalive scripts, diagnose remote access issues. Instead of hunting through notes or SSH-ing and fumbling around, I wanted one tool. A menu. Same commands, same approach, any distro. Works local or remote. I can call it from my home bin folder and it just works. ...

G4 desktop, Fedora 44 on SDA. Decided to try RakuOS on a spare NVMe. Booted the G4 again and Fedora wouldn’t boot from SDA. The EFI entry exists. The files are there. But the UEFI firmware just skips SDA and boots something else. understanding the problem Your computer’s EFI system (UEFI firmware) has a boot order list. That list points to files on disk that tell the firmware how to boot each OS. If that pointer gets broken or the bootloader itself isn’t properly initialized, the entry becomes dead weight. It exists but doesn’t work. ...

Fedora 44, KDE Plasma, Wayland session. Simple thing, holding a key down. 7777777777777777777 Except it wasn’t doing that anymore. Hold 7, get one 7, and instead of it repeating I’d get a little popup underneath the cursor with a handful of characters sitting in it. Looked exactly like one of those mobile long-press accent menus. Checked System Settings → Input Devices → Keyboard → Key repeat. All fine, delay and rate both set correctly. Tried the Test area right there in Settings, same thing happened, single character then that popup. Tried it in a terminal, tried it in the browser, tried it in an editor. Everywhere. Not one app misbehaving, the whole session. ...