Goofed Home

For years, many Ubuntu users have felt that traditional .deb packages were being gradually sidelined in favor of the Snap ecosystem.

It started quietly. Double-clicking a downloaded .deb file would open it in Archive Manager instead of the installer. Then came controversial changes. Apps like Chromium, Thunderbolt and Firefox began defaulting to Snap packages, even when users tried installing them via the apt command in the terminal.

It continued further as Ubuntu introduced its new Snap Store. In Ubuntu 24.04, it ignored .deb packages completely. Double-clicking a .deb file would open the App Center, but wouldn’t actually install the package and just hang there. That behavior was later reverted after I highlighted it through It’s FOSS.

Agreed, but how many requests do you see for support for people understanding mesh networking enough to set a server up in docker? Those are the people that use it and need it, and surprise they use docker, not flatpack or snap.

I am talking about non powerusers, non it personnel that are installing steam or gimp via snap or flatpack and then flood support threads with their problems. In those cases sandboxing is fucking stupid.

It’s also really easy to avoid the company that made the slow, propietary, corporate-owned Snaps default as a slap-in-face to the open-source community they depend on.

Maybe they should implement something beyond toy security.

KaOS Linux 2026.03 has been released today as the ISO snapshot for March 2026 of this independent Linux distro using Arch Linux’s pacman package manager.

Last month, when KaOS Linux 2026.02 was released, we reported that the distribution had dropped its KDE/Plasma desktop environment, after more than 12 years using it as the default, in favor of a Niri/Noctalia setup to avoid any use the systemd init system and move to Dinit instead.

Now, the KaOS Linux 2026.03 release is here to strip more systemd-related components from the distribution in an attempt to become a systemd-free distro. As such, the devs removed the systemd-boot bootloader component, along with mkinitcpio, which was replaced with Dracut for initramfs creation.

Huh, they’re not doing digital ID ‘round those parts either.

Good.

kaOS linux? Sounds made up by some LLM.

I run CachyOS on my desktop. I host Homepage for myself on a home server. This is reached at home.mydomain.tld. Pihole on my local network catches that request and points it at my local nginx, which reverse proxies me to the homepage.

Now, I set this all up a while back and it all worked totally fine for several weeks. Then, about a week or so ago, for some reason almost every, but not every time I boot my PC, home.mydomain.tld gives me a “cannot be reached” error in my browser… until I run systemctl restart NetworkManager and then it works completely normally.

Can anyone help me troubleshoot why oh why that would suddenly be a thing? Does anyone have suggestions of a way I can troubleshoot a permanent fix to this so that I don’t have to restart NetworkManager almost every boot?

Nice, narrowing it down!

Next thing I would check is your configured DNS servers on the desktop, it needs to have only the pihole IP, if it has any other servers configured that is likely the issue.

Also worth pinging the pihole IP next time it’s not working, to check if it’s actually a networking issue instead of a DNS issue.

It’s normal for the loopback con path to end in 1, each con path is unique for each interface. My guess is that if your pihole sometimes works, the IPv4 server is your pihole and the IPv6 servers are ISP provided (especially if there are 2), so they work for the internet but not your internal network. Ideally you would set your pihole’s IPv6 address as your IPv6 DNS as well. Failing that setting the IPv6 mode to “Automatic, addresses only” will make it not used for DNS

Cool I guess. Tubi sucks ass though.

Came to comment this.

Inserting ads into legacy PBS programming is sacrilege.

@dineinfr thanks, I'll check!