Fedora Atomic variants just differ in the desktop environments.

You can see Universal Blue stuff here: https://universal-blue.org/. But in short, Bazzite is for gaming and the others are for regular desktop uses. All have a “batteries-included” attitude. There’s also some images meant for servers.

Debian 12.7 is a year old. You’re supposed to upgrade to the latest version (currently 12.11) before doing the upgrade.

We have to wait and see if it’s really mediocre. Gnome Web certainly has performance issues, but those may be due to WebkitGTK.

Orion is not using WebkitGTK, despite using GTK and Libadwaita. Their port may not have the same performance issues.

And when I say performance issues, I don’t mean benchmarks. Gnome Web actually does pretty decent on benchmarks, but things like scrolling with a mouse just don’t feel smooth (but do with a trackpad).

This also affects dnf since OpenH264 is distributed from Cisco’s server’s, not Fedora’s.

You can follow this blog post: https://yselkowitz.github.io/blog/2025/08/12/openh264-fedora-flatpaks.html

Should be fine with option 1. Just need to install flatpak-module-tools beforehand.

Discovers talks to PackageKit, a project that attempts to abstract packaging concepts. So rather than Discover supporting dnf, apt, pacman, etc, it talks to PackageKit and that handles the lower level stuff.

But PackageKit is not perfect. It’s better to use dnf directly and use the flag for offline upgrades (for more reliable upgrades).

Maybe. The thing is that Electron is not made by Google. There’s always a chance that downstream they may still default to X11.

Chromium defaults to using X11, even on Wayland. By setting the ozone hint to auto, it will then default Wayland users to using Chromium’s Wayland backend.

It’s resolved now.

Fedora Flatpaks are better in this regard. They are built entirely from Fedora rpms. When an rpm gets updated in the Fedora repos, rebuilding the flatpak will automatically pull in that updated rpm. And with flatpak’s deduplication feature, any reused vendored dependency should be perfectly deduplicated since the input is exactly the same (the rpm).

The problem just is that the repo is small, it’s affected by Fedora’s risk-averseness (so no codecs), and people don’t like them.

Yes

Gnome article on same topic: https://blogs.gnome.org/shell-dev/2024/09/20/understanding-gnome-shells-focus-stealing-prevention/

You can test the more strict focus stealing prevention on Gnome with: gsettings set org.gnome.desktop.wm.preferences focus-new-windows ‘strict’.

And to unset it: gsettings set org.gnome.desktop.wm.preferences focus-new-windows ‘smart’

Firefox should also now have proper support for it in 141, but I think for Gnome you might need to wait for a bug fix in Gnome 49:

Is there a pixel device with a jack port?

None that are still supported by GrapheneOS. But you can buy a USB-C to 3.5mm jack dongle.

My main OS is debian. How easy is to transfer data from GrapheneOS to debian and the other way round?

Pretty easy, either by cable or using an app like LocalSend (they have an apk on their Github).

Overall if you run GrapheneOS on a pixel, how many years running it and what do you think about it?

Haven’t used it in a while. I think it was cool, but was definitely more of a hassle than regular Android. The default apps are pretty barebones and feel old. Though I do still dream about replacing my iPhone with a device with GrapheneOS.

Yeah. I’ve used NixOS and think the idea is cool, but overall I prefer Fedora Atomic. Unlike NixOS, it’s a complete OS out of the box and is less quirky than NixOS. Though I am a proponent of Flatpak, those who don’t like it will have a very different opinion of Fedora Atomic.

I just wish Fedora Atomic was more declarative and that bootc could work a bit closer to how NixOS’s nix.conf worked. I would love if that there was a a container file could be declared and used built similarly to nix.conf is (avoiding the user manually building the and signing the container file).

That kinda exists with NixOS, but you’d have to backup your personal files separately.

You’re not really backing up the OS with NixOS, but the nix configuration file describes how the OS is built in a reproducible way.

Or do you just remember all the config changes you did and type them out from the top of your head? And all the apps you have installed? It’s over 300 apps and 100 config files for me.

Well, kinda. I have have scripts to set up most of my system after an installation. It’s nice so that I don’t have to remember everything I’ve done. It means I can reinstall my system or install on a new system with relative ease.

Doesn’t need to be anything complex. Just having a list of packages I want installed and that I can copy into my terminal makes things so much faster.

Timeshift is completely unnecessary. Fedora Atomic’s rollbacking is more powerful and avoids certain issues.

You should only be backing up personal files, not OS files. The OS is replaceable, your personal files are not.

The only issue I’ve had with LocalSend is that it’s a bit buggy on iOS. If you leave the app open in the background and go back to it, it won’t be able to receive files. I have to force quit it and open it again to fix it.

I don’t think nonfree is enabled by default. Though I guess the repos are still hosted by debian, unlike RPMFusion. Though Fedora does treat it as semi-official given that parts of it can be enabled during first setup.

Fedora and Debian have similar philosophies. FOSS only, packages must be built from source, no vendored dependencies. So they have similar policies regarding security and Fedora Flatpaks align closer to that than Flathub.

I believe Debian also doesn’t ship patented codecs in their main repo.