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.

Depends what you mean by “problem”. The biggest problem with traditional packages like debs and rpms is that compatibility sucks. They only reliably run on the distro and version they are designed for. Third party packages typically build on old dependencies and hope that backwards compatibility will allow them to run without issue on later distro versions.

Yes, it’s redundant to have have the same app packaged as flatpaks. Though I don’t think that redundancy is necessarily a bad thing. Flathub is not a profitable project and has up to this point relied on Gnome for funding. There’s work being done to spin it out to be it’s own thing and hopefully be supported by paid apps. But what if that fails and it shuts down? Or less dramatically, what if Flathub has a major outage?

One of the common complaints against snap is that there is only one store, controlled by Canonical. Flatpak is designed to support multiple stores. I don’t see why they can’t exist side by side. That’s exactly what I do. I have dozens of apps installed from each source.

And to address the claim of what if “each distro decides to make a flatpak repo according to their own philosophies?”. I guess that would depend on how many resources are being poured into supporting that. If flatpak continues to push for OCI support, then that would make it easier for distros to have their own remotes, if they desire. If not, they can just use an existing option. Whether that be Flathub or Fedora. Personally, I think Fedora Flatpaks are a good match for Debian and OpenSUSE’s policies, only real downside is that major Gnome app updates would be a month delayed, annoying Tumbleweed users.

There are broken Flatpaks in Flathub too. Does Flathub deserve legal threats too? No.

Not distro specific. They are Flatpaks built according to Fedora’s philosophy. But you can use them anywhere. I’ve used them on Ubuntu and OpenSUSE.

Last update (which replaced Discover with Bazaar) changed that.

In a way, true. But I don’t think they are using flatpak’s filter mechanism. I believe the filtering is done by Bazaar itself. That means that even if Bazaar is hiding an app, you are still able to install it manually from the CLI.

The intent is also different. Bazaar is filtering out footguns, like the Steam flatpak on Bazzite (since Steam is preinstalled as an RPM) and Bluefin hides flatpak IDEs.

All FLOSS apps on Flathub are built on trusted platforms by default, in the open and verifiable.

That’s not true. Take LocalSend as an example. It does not build LocalSend on Flathub. It simply takes a GitHub release URL of a compiled tar.gz. And GitHub releases do not have to be built on GitHub, you are able to upload any local file and have it shown as a release.

The sudden success of Bazzite comes from how easy it is to use.

I agree. But it’s also important to have principles and to stick to them. The great thing about Fedora Atomic is that Fedora is able to create their FLOSS OS following their principles and others are able to take that base and build upon it to create their vision.

Fedora doesn’t have to be for everyone.

What OBS did was bad. They should not have stuck to an EOL runtime, period. It would have been better if they temporarily moved to a supported freedesktop runtime and vendored in their Qt dependencies. That way, they would have been using a supported runtime while still using their outdated Qt version until the upstream issues were fixed.

Not at all.

• Bazzite preinstalls Flathub apps by default. The author still wants to use Fedora Flatpaks for the preinstalled apps.
• Bazzite ships Flathub unfiltered. The author wants to only show FLOSS software built on trusted platforms by default (so no taking a precompiled binary and shipping that).
• Bazzite ships Flathub in spite of its flaws. The author wants Fedora to work with Flathub to clean up its issues before shipping the remote by default.