<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>noratek.blog — technical logbook</title><description>Said Eloudrhiri&apos;s hands-on HOWTOs and fixes for Linux, terminals, networking, security and developer tooling.</description><link>https://noratek.blog/</link><language>en</language><item><title>Switch the macOS keyboard layout automatically per keyboard (Karabiner-Elements)</title><link>https://noratek.blog/howto/macos-per-keyboard-input-source-karabiner/</link><guid isPermaLink="true">https://noratek.blog/howto/macos-per-keyboard-input-source-karabiner/</guid><description>Make macOS pick the right input source for whichever keyboard you actually type on — French (Mac) for the built-in and Apple keyboards, French-PC for a Keychron V6 Max — using two Karabiner-Elements rules, plus the two traps that silently break it: keyboards that also declare themselves as pointing devices, and the console user server not restarting after a Karabiner update.</description><pubDate>Sun, 06 Sep 2026 00:00:00 GMT</pubDate><atom:updated>2026-09-06T00:00:00.000Z</atom:updated><category>macos</category><category>karabiner</category><category>keyboard</category><category>input-source</category><category>keyboard-layout</category><category>launchd</category><category>troubleshooting</category></item><item><title>Boot into Btrfs snapshots from GRUB on Fedora (grub-btrfs + snapper)</title><link>https://noratek.blog/howto/grub-btrfs-boot-into-snapshots-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/grub-btrfs-boot-into-snapshots-fedora/</guid><description>Add a &apos;Fedora Linux snapshots&apos; submenu to the GRUB boot screen so you can boot directly into a snapper snapshot when the system won&apos;t start after a bad update — the recovery case plain snapper can&apos;t cover because it needs a working system to log into. grub-btrfs is not in Fedora&apos;s repos, so it comes from the kylegospo COPR; a grub-btrfs watcher unit regenerates the menu whenever snapper adds/removes a snapshot. Three gotchas covered: the packaged grub-btrfs.path unit binds to a .snapshots.mount unit that exists only when /.snapshots is separately mounted, so a nested /.snapshots needs a local systemd override; making a rollback permanent cannot use &apos;snapper rollback&apos;, which is silently ignored on a Fedora install that pins subvol=root — the subvolume swap is the procedure that works; and menu generation fails silently, with no output whatsoever, when run from a directory root cannot enter (a FUSE mount such as an rclone-mounted ~/Dropbox), leaving grub2-probe to abort with &apos;cannot restore the original directory&apos;. Includes the important separate-/boot caveat (kernel/initramfs live on an ext4 partition and are NOT snapshotted) and read-only snapshot boot. Also covers Fedora&apos;s menu_auto_hide mechanism: hide the boot menu on healthy boots while it reappears on its own after a failed one, so the snapshot entries are there exactly when they are needed — plus how to summon it on demand for a deliberate rollback. Optional follow-on to the snapper setup.</description><pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>grub-btrfs</category><category>grub2</category><category>snapper</category><category>btrfs</category><category>snapshots</category><category>rollback</category><category>boot</category><category>recovery</category><category>copr</category><category>fedora</category><category>bls</category></item><item><title>Dropbox online-only on Fedora 44 with rclone</title><link>https://noratek.blog/howto/rclone-dropbox-online-only-fedora-44/</link><guid isPermaLink="true">https://noratek.blog/howto/rclone-dropbox-online-only-fedora-44/</guid><description>Get an online-only Dropbox workflow (similar to Smart Sync on Mac/Windows) on Fedora via an rclone FUSE mount driven by a systemd-user service, with on-demand VFS cache and automatic upload.</description><pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>rclone</category><category>dropbox</category><category>fuse</category><category>systemd</category><category>fedora</category></item><item><title>Snapper restore points on Fedora (Btrfs) with auto snapshots before every dnf transaction</title><link>https://noratek.blog/howto/snapper-btrfs-restore-points-dnf-hook-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/snapper-btrfs-restore-points-dnf-hook-fedora/</guid><description>Install and configure snapper on a Fedora Btrfs-on-LUKS system to create filesystem restore points: a root config with hourly timeline snapshots and auto-cleanup, plus automatic pre/post snapshots around every dnf transaction. Fedora 44 uses dnf5, which has no snapper plugin, so the dnf hook is wired up with the libdnf5 &apos;actions&apos; plugin calling a small wrapper script that labels snapshots by operation (dnf install / upgrade / remove). Covers what a root config does and does not capture on Fedora&apos;s multi-subvolume layout, why /.snapshots belongs in a top-level subvolume rather than nested inside root, and — the part most guides get wrong — why &apos;snapper rollback&apos; cannot work on a Fedora install that pins subvol=root in fstab and on the kernel command line, with the subvolume-swap procedure that does.</description><pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-14T00:00:00.000Z</atom:updated><category>snapper</category><category>btrfs</category><category>snapshots</category><category>restore-points</category><category>dnf5</category><category>libdnf5-actions</category><category>fedora</category><category>luks</category><category>backup</category><category>rollback</category><category>subvolumes</category></item><item><title>Flatpak apps won&apos;t start on Fedora — a hung Keybase FUSE mount (/keybase)</title><link>https://noratek.blog/howto/keybase-fuse-mount-blocks-flatpak-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/keybase-fuse-mount-blocks-flatpak-fedora/</guid><description>Extension Manager (and every other Flatpak app) hangs forever at launch with unkillable processes. The cause is not the app: it is the Keybase redirector&apos;s dead FUSE mount on /keybase, which Flatpak stats while building its sandbox. How to identify it, unblock it without rebooting, and remove Keybase for good.</description><pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-05T00:00:00.000Z</atom:updated><category>fedora</category><category>flatpak</category><category>fuse</category><category>keybase</category><category>gnome</category><category>troubleshooting</category></item><item><title>Drive both Framework Laptop 16 LED Matrix modules as a live system monitor on Fedora</title><link>https://noratek.blog/howto/framework16-led-matrix-system-monitor-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/framework16-led-matrix-system-monitor-fedora/</guid><description>Turn the two Framework Laptop 16 LED Matrix input modules into stable left/right displays showing live CPU, memory, temperature and fan metrics — as bars, as figures or as pictograms — configured from a TOML file, re-read on the fly, with power-aware blanking and a systemd user service.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-08-02T00:00:00.000Z</atom:updated><category>framework</category><category>led-matrix</category><category>hwmon</category><category>cros_ec</category><category>systemd</category><category>udev</category><category>toml</category><category>fedora</category></item><item><title>Skip fingerprint auth when the laptop lid is closed (fprintd) on Fedora</title><link>https://noratek.blog/howto/fprintd-skip-when-lid-closed-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/fprintd-skip-when-lid-closed-fedora/</guid><description>Docked with the lid shut, every sudo/su/polkit prompt still tries the unreachable fingerprint reader first and makes you wait. Put a tiny lid check in front of pam_fprintd via pam_exec so PAM skips fingerprint and goes straight to the password prompt when the lid is closed — instantly, no daemon, reusing your existing enrolled prints.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-19T00:00:00.000Z</atom:updated><category>fedora</category><category>fingerprint</category><category>fprintd</category><category>pam</category><category>authselect</category><category>pam-exec</category><category>lid</category><category>laptop</category></item><item><title>An ML4W-style Kitty config on Fedora: native tabs, splits, and Tokyo Night</title><link>https://noratek.blog/howto/kitty-ml4w-style-config-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/kitty-ml4w-style-config-fedora/</guid><description>Recreate the terminal experience from ML4W (My Linux for Work) — Kitty with native tabs and splits, a powerline tab bar, a JetBrainsMono Nerd Font, the Tokyo Night theme, and the Fastfetch system-info greeting on launch — on a plain Fedora GNOME desktop, no Hyprland or tmux required.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-19T00:00:00.000Z</atom:updated><category>kitty</category><category>terminal</category><category>ml4w</category><category>fastfetch</category><category>tokyo-night</category><category>nerd-font</category><category>fedora</category></item><item><title>Give Ptyxis a Starship powerline prompt with a Tux logo on Fedora</title><link>https://noratek.blog/howto/ptyxis-starship-tux-prompt-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/ptyxis-starship-tux-prompt-fedora/</guid><description>Turn Fedora&apos;s default Ptyxis terminal into a polished setup: a JetBrainsMono Nerd Font, a Starship powerline prompt, and a leading OS glyph swapped from the Fedora mark to the Tux penguin.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-19T00:00:00.000Z</atom:updated><category>ptyxis</category><category>starship</category><category>terminal</category><category>nerd-font</category><category>fedora</category><category>gnome</category></item><item><title>Chrome won&apos;t start after renaming your machine (hostname change) on Fedora</title><link>https://noratek.blog/howto/chrome-wont-start-after-hostname-change-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/chrome-wont-start-after-hostname-change-fedora/</guid><description>Google Chrome silently fails to launch after a hostname change. The cause is a stale SingletonLock symlink in the user profile that still encodes the old machine name; deleting the Singleton* lock files restores normal startup. Applies to every Chromium-based browser and Electron app.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-18T00:00:00.000Z</atom:updated><category>fedora</category><category>google-chrome</category><category>chromium</category><category>hostname</category><category>troubleshooting</category><category>linux-desktop</category><category>profile-lock</category></item><item><title>Flutter development environment on Fedora 44 (mise + Android Studio)</title><link>https://noratek.blog/howto/fedora-mise-flutter-android/</link><guid isPermaLink="true">https://noratek.blog/howto/fedora-mise-flutter-android/</guid><description>Set up a complete Flutter toolchain on Fedora 44 / GNOME using mise as the runtime version manager, with the Android SDK in the default ~/Android/Sdk so flutter doctor detects it without extra configuration — ending with &apos;No issues found&apos; across Android, web and Linux desktop targets.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-18T00:00:00.000Z</atom:updated><category>fedora</category><category>flutter</category><category>dart</category><category>mise</category><category>android</category><category>android-studio</category><category>intellij</category><category>zsh</category></item><item><title>macOS-style screenshot shortcuts on GNOME (Fedora)</title><link>https://noratek.blog/howto/gnome-macos-screenshot-shortcuts/</link><guid isPermaLink="true">https://noratek.blog/howto/gnome-macos-screenshot-shortcuts/</guid><description>Replicate the macOS screenshot key bindings (Cmd+Shift+3/4/5) on GNOME so muscle memory carries over from a MacBook — including the non-obvious part: Dash to Dock silently steals Super+Shift+N, and the pre-GNOME 42 gsettings keys no longer exist.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-18T00:00:00.000Z</atom:updated><category>gnome</category><category>wayland</category><category>keybindings</category><category>gsettings</category><category>dash-to-dock</category><category>screenshot</category><category>macos</category><category>fedora</category></item><item><title>Install Claude Code on Fedora Linux with dnf (zsh)</title><link>https://noratek.blog/howto/install-claude-code-fedora-zsh/</link><guid isPermaLink="true">https://noratek.blog/howto/install-claude-code-fedora-zsh/</guid><description>Install Claude Code on Fedora from Anthropic&apos;s signed dnf repository (the recommended method on Fedora/RHEL), configure it for zsh, migrate off a curl|bash native install, and demystify the &quot;Update available!&quot; banner that the stable channel triggers.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-18T00:00:00.000Z</atom:updated><category>claude-code</category><category>anthropic</category><category>fedora</category><category>dnf</category><category>zsh</category><category>rpm</category><category>installation</category></item><item><title>Login screen keyboard layout stays QWERTY on Debian/Ubuntu</title><link>https://noratek.blog/howto/login-screen-keyboard-layout-stays-qwerty-debian-ubuntu/</link><guid isPermaLink="true">https://noratek.blog/howto/login-screen-keyboard-layout-stays-qwerty-debian-ubuntu/</guid><description>The desktop session uses the right keyboard layout, but the display manager greeter is still QWERTY. On Debian and Ubuntu the system-wide layout lives in /etc/default/keyboard and is applied by console-setup — localectl set-x11-keymap is deliberately disabled on these distributions.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-18T00:00:00.000Z</atom:updated><category>debian</category><category>ubuntu</category><category>keyboard</category><category>xkb</category><category>console-setup</category><category>gdm</category><category>display-manager</category></item><item><title>Login screen keyboard layout stays QWERTY on systemd distributions (Fedora, RHEL, Arch, openSUSE)</title><link>https://noratek.blog/howto/login-screen-keyboard-layout-stays-qwerty-systemd-distros/</link><guid isPermaLink="true">https://noratek.blog/howto/login-screen-keyboard-layout-stays-qwerty-systemd-distros/</guid><description>The greeter of GDM, SDDM or LightDM ignores the layout configured in the desktop session. On localectl-driven distributions the fix is a single command that writes /etc/X11/xorg.conf.d/00-keyboard.conf — which Wayland greeters read too, via xkbcommon.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-18T00:00:00.000Z</atom:updated><category>fedora</category><category>arch</category><category>opensuse</category><category>keyboard</category><category>xkb</category><category>localectl</category><category>gdm</category><category>sddm</category><category>wayland</category></item><item><title>Stop Claude Code from hijacking mouse clicks (fullscreen mouse capture) on Linux &amp; macOS</title><link>https://noratek.blog/howto/claude-code-disable-mouse-clicks/</link><guid isPermaLink="true">https://noratek.blog/howto/claude-code-disable-mouse-clicks/</guid><description>Since fullscreen rendering, Claude Code captures the mouse — clicking in the prompt moves the cursor and a stray click can hit &apos;Ask something&apos; or a menu option (very easy to do by accident in the JetBrains/IntelliJ terminal). Disable click/drag/hover while keeping wheel scroll with CLAUDE_CODE_DISABLE_MOUSE_CLICKS=1, or kill mouse capture entirely with CLAUDE_CODE_DISABLE_MOUSE=1. There is no settings.json field and no CLI flag — only these environment variables — and a running session must be restarted to pick them up.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><atom:updated>2026-07-07T00:00:00.000Z</atom:updated><category>claude-code</category><category>terminal</category><category>mouse</category><category>fullscreen</category><category>tui</category><category>jetbrains</category><category>intellij</category><category>fedora</category><category>macos</category><category>env-var</category></item><item><title>Fix fwupd UEFI dbx update failing with &quot;Not enough efivarfs space&quot; on a Framework 16 (AMD)</title><link>https://noratek.blog/howto/fwupd-dbx-efivarfs-space-framework16-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/fwupd-dbx-efivarfs-space-framework16-fedora/</guid><description>fwupdmgr refuses the UEFI dbx (Secure Boot revocation list) update with &quot;does not currently allow updates: Not enough efivarfs space, requested 30,7 kB and got 20,0 kB&quot;. The NVRAM variable store is full of legitimate, fragmented Secure Boot key data — the new dbx is larger than the free slot. Diagnose it safely with efivar/efibootmgr, understand why deleting boot entries or efivars does not help, and apply the proven fix: erase and restore Secure Boot keys to defaults in the BIOS, which repacks (defragments) the variable store. Tested on a Framework 16 AMD 7040 / Fedora 44, fwupd 2.1.5.</description><pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-27T00:00:00.000Z</atom:updated><category>framework</category><category>fwupd</category><category>dbx</category><category>uefi</category><category>secure-boot</category><category>efivarfs</category><category>efivars</category><category>nvram</category><category>fedora</category></item><item><title>Check the BIOS version of a Framework Laptop on Linux (dmidecode)</title><link>https://noratek.blog/howto/framework-laptop-bios-version-linux/</link><guid isPermaLink="true">https://noratek.blog/howto/framework-laptop-bios-version-linux/</guid><description>Read the running BIOS/UEFI firmware version of a Framework Laptop from Linux with dmidecode — install it on Ubuntu or Fedora, interpret every field (vendor, version, release date, ROM size, CPU family.model.stepping), cross-check with lshw and sysfs, and compare against the latest Framework release with fwupd before flashing.</description><pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-25T00:00:00.000Z</atom:updated><category>framework</category><category>bios</category><category>uefi</category><category>dmidecode</category><category>lshw</category><category>fwupd</category><category>ubuntu</category><category>fedora</category></item><item><title>Build an auto-deploying static blog: Astro + a private content repo + OVH (GitHub Actions over SFTP)</title><link>https://noratek.blog/howto/build-auto-deploying-astro-blog-ovh/</link><guid isPermaLink="true">https://noratek.blog/howto/build-auto-deploying-astro-blog-ovh/</guid><description>End-to-end recipe for a 100% static Astro blog whose content lives in a separate private GitHub repo, auto-cleaned at build time and deployed to OVH shared hosting over SFTP via GitHub Actions — covering OVH multisite, DNS/SSL, secrets, a push-to-publish loop, and the gotchas that actually bite.</description><pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-21T00:00:00.000Z</atom:updated><category>astro</category><category>ovh</category><category>github-actions</category><category>ci-cd</category><category>sftp</category><category>lftp</category><category>static-site</category><category>deployment</category><category>pagefind</category><category>mermaid</category></item><item><title>macOS-style Super+C / Super+V copy-paste everywhere on Fedora GNOME (incl. Ptyxis terminal)</title><link>https://noratek.blog/howto/macos-super-copy-paste-fedora-gnome/</link><guid isPermaLink="true">https://noratek.blog/howto/macos-super-copy-paste-fedora-gnome/</guid><description>Remap the Super key so Super+C/V/X copy/paste/cut in every app and in the Ptyxis terminal on Fedora GNOME Wayland, just like Cmd+C/V on macOS.</description><pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-21T00:00:00.000Z</atom:updated><category>fedora</category><category>gnome</category><category>wayland</category><category>keyd</category><category>ptyxis</category><category>keyboard</category><category>clipboard</category><category>macos</category></item><item><title>git clone / SSH to GitHub hangs on Fedora + GNOME (gcr-ssh-agent)</title><link>https://noratek.blog/howto/ssh-git-github-hangs-fedora-gnome/</link><guid isPermaLink="true">https://noratek.blog/howto/ssh-git-github-hangs-fedora-gnome/</guid><description>git/ssh to GitHub hangs because GNOME&apos;s gcr-ssh-agent freezes when signing passphrase-protected keys and keeps re-hijacking SSH_AUTH_SOCK; fix by running an OpenSSH ssh-agent user service, exporting its socket via environment.d, and masking gcr-ssh-agent.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-16T00:00:00.000Z</atom:updated><category>ssh</category><category>github</category><category>git</category><category>fedora</category><category>gnome</category><category>ssh-agent</category><category>gnome-keyring</category><category>systemd</category></item><item><title>Framework Laptop 16 keyboard backlight pulses on/off by itself on Fedora</title><link>https://noratek.blog/howto/framework16-keyboard-backlight-pulsing-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/framework16-keyboard-backlight-pulsing-fedora/</guid><description>The FW16 white keyboard backlight self-toggles because of the QMK breathing effect; disable it with qmk_hid (built from source on Fedora).</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-14T00:00:00.000Z</atom:updated><category>framework</category><category>keyboard</category><category>backlight</category><category>fedora</category><category>qmk</category><category>rust</category></item><item><title>Framework Laptop 16 — keyboard backlight in GNOME (Fedora 44)</title><link>https://noratek.blog/howto/fw16-keyboard-backlight-gnome/</link><guid isPermaLink="true">https://noratek.blog/howto/fw16-keyboard-backlight-gnome/</guid><description>Wire the FW16&apos;s separate QMK keyboard backlight into native GNOME control (Quick Settings slider + brightness keys) via a kernel uleds virtual LED and a qmk_hid bridge daemon.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-14T00:00:00.000Z</atom:updated><category>framework</category><category>keyboard</category><category>backlight</category><category>gnome</category><category>fedora</category><category>qmk</category></item><item><title>Ghostty crashes on Fedora 44 → switching to Ptyxis (with Starship)</title><link>https://noratek.blog/howto/ghostty-crash-fedora-switch-to-ptyxis/</link><guid isPermaLink="true">https://noratek.blog/howto/ghostty-crash-fedora-switch-to-ptyxis/</guid><description>Ghostty 1.3.1 crashes at startup on Fedora 44 (a Linux-only bundled-fontconfig/glycin symbol clash); switch to Ptyxis — Starship is shell-side so it carries over, only login-shell and a Nerd Font need setting.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-14T00:00:00.000Z</atom:updated><category>ghostty</category><category>ptyxis</category><category>terminal</category><category>starship</category><category>fedora</category></item><item><title>Ghostty Crash on Claude / TUI Output — fontconfig Cache Fix (Fedora)</title><link>https://noratek.blog/howto/ghostty-fontconfig-crash-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/ghostty-fontconfig-crash-fedora/</guid><description>Ghostty segfaults when a TUI app prints glyphs that need font fallback, caused by a corrupt user fontconfig cache holding mismatched cache-N versions; clear ~/.cache/fontconfig and rebuild to fix.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-14T00:00:00.000Z</atom:updated><category>ghostty</category><category>fontconfig</category><category>terminal</category><category>crash</category><category>fedora</category></item><item><title>GNOME keeps asking to unlock the Login keyring after fingerprint login (Fedora)</title><link>https://noratek.blog/howto/gnome-keyring-fingerprint-login-prompt/</link><guid isPermaLink="true">https://noratek.blog/howto/gnome-keyring-fingerprint-login-prompt/</guid><description>After fingerprint login GNOME repeatedly prompts to unlock the password-encrypted Login keyring; the practical workaround (LUKS required) is to remove the keyring password so it auto-unlocks at session start.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-14T00:00:00.000Z</atom:updated><category>gnome</category><category>keyring</category><category>fingerprint</category><category>security</category><category>fedora</category></item><item><title>Changing the LUKS Disk Encryption Passphrase on Fedora</title><link>https://noratek.blog/howto/fedora-luks-change-passphrase/</link><guid isPermaLink="true">https://noratek.blog/howto/fedora-luks-change-passphrase/</guid><description>Change a Fedora LUKS2 full-disk-encryption passphrase on a live, mounted system (header backup, luksChangeKey or add-then-kill keyslot) with no reboot or reinstall required.</description><pubDate>Sat, 13 Jun 2026 00:00:00 GMT</pubDate><atom:updated>2026-06-13T00:00:00.000Z</atom:updated><category>luks</category><category>encryption</category><category>cryptsetup</category><category>security</category><category>fedora</category></item><item><title>Diagnosing Bandwidth Saturation — Fedora</title><link>https://noratek.blog/howto/bandwidth-saturation-diagnostic-fedora/</link><guid isPermaLink="true">https://noratek.blog/howto/bandwidth-saturation-diagnostic-fedora/</guid><description>Cascading method to pinpoint the process, device, or protocol family responsible for abnormally low Internet throughput on Fedora (speedtest, nethogs, iftop, iw).</description><pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate><atom:updated>2026-05-09T00:00:00.000Z</atom:updated><category>network</category><category>bandwidth</category><category>diagnostic</category><category>wifi</category><category>fedora</category></item><item><title>IPv6 Troubleshooting — Fedora behind Orbi + Proximus BBx</title><link>https://noratek.blog/howto/ipv6-troubleshooting-fedora-proximus/</link><guid isPermaLink="true">https://noratek.blog/howto/ipv6-troubleshooting-fedora-proximus/</guid><description>Diagnose and fix broken IPv6 (slow browsing via Happy Eyeballs) on Fedora behind an Orbi in double NAT on a Proximus BBx, from the NetworkManager workaround to the Orbi pass-through fix and PMTUD.</description><pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate><atom:updated>2026-05-09T00:00:00.000Z</atom:updated><category>ipv6</category><category>network</category><category>dns</category><category>proximus</category><category>fedora</category></item></channel></rss>