Not sure what the title was before you changed it, but if I see a post in my feed that looks like this (without the "very bad take" part), I wouldn't even want to open the post to see the description. I'm glad you clarified by editing the title, but without making your stance clear in the title from the very beginning, it would be bound to receive a barrage of downvotes.

This is a bit late, but I just wanted to follow up to let you know that Fedora 40 updated to kernel 6.9 last week.

Fedora has pretty good SELinux configured out of the box, and isn't focused on opsec. It's just sane defaults and proper limitations to access. It also switched to Walyand-by-default this release, completely removing X11 from the default packages, which mitigates many of the "app spying on other app" scenarios that a previous user in the thread was talking about. That's not to say that Fedora is the pinnacle of Linux security or anything, but it comes with pretty good defaults for the average user. You'd have to get into kernel hardening and deep into SELinux to do better as an end user, which is not something that most users are inclined to spend time or energy on.

Seconding partclone here, it's the easiest solution for imaging that only backs up the data on the partition that is used. Plus, it's in RescueZilla, which is pretty intuitive and user friendly for those that prefer GUIs

Shouldn't be too long left, I'd expect it to hit Fedora 40 sometime this month. I also shared instructions on how to temporarily upgrade the kernel to the one in Fedora 41's repos (which is past 6.9) if you were interested in trying that, though the instructions are untested as of yet (the issue doesn't affect me since I don't play games). It's easily revertible if you wanted to give it a try. I probably wouldn't bother if you use secure boot, because I've had issues with signing things before with similar steps, though those are the official steps from the Fedora documentation, so it may be that they just work fine.

Is it related to the issue described in the post attached to this comment? The linked comment also links to an issue page with details about the issue the poster experienced. If so, then that issue should actually be fixed in kernel 6.9 (which still has not been added to the Fedora 40 repos), and not caused by it.

An extension of this issue is present in 6.8.9+ before 6.9, which is why I ask if this seems to be related (since the versions are pretty close in time and Fedora doesn't even have 6.9 yet).

It really depends on the individual case. There are many CS professions where the title "engineer" or "scientist" is incredibly accurate. I believe that is a minority of course, and further depends on how broad your definition of "cs people" is. There are specialties within the incredibly broad field of computer science that require education in classical engineering, as well as specialties that focus on research and experimentation with the scientific method.

Hm, it could be a new issue then. I'm not seeing it on the Bazzite issues page, perhaps you should open a new issue on it here, and provide your hardware specs. At the very least, you could see if this issue is reproducible on other installs, and someone there could help to obtain more useful debug info to determine the actual problem. You could also report it on the Mozilla Bugzilla page, as chances are this is a Firefox issue and not a Bazzite issue, but I admit that the interface for bug reports is less intuitive for non-developers there. Bazzite devs would likely direct you to there first anyway though.

All I can really say myself is that I don't experience this on Fedora Atomic KDE 40.20240607 with Mullvad Browser or the Firefox flatpak. I suspect it is either a hardware/config issue (on fresh install, I'd say a config issue is a distro issue if you haven't changed anything), or that this is Bazzite specific and not present in upstream Fedora Atomic. Regardless, it's a good idea to report this so that other users don't experience the same bug

Sounds about in line with what I'd expect. If that works for you where the flatpak doesn't, then it at least makes a viable solution for the short term (though I don't know how much overhead would be introduced). A minute of delay is ridiculously long for startup, so I still don't know why you were having that issue with the flatpak

Is it? I was looking a few months ago at Nix support in Fedora Atomic (which Bazzite is based on), and it required some minor hacks to get the /nix folder and Nix itself working properly with rpm-ostree distros, as root is otherwise immutable. Plus, Nix isn't available by default in the Fedora repos it seems. I believe it required something along the lines of making a /var/nix folder and symlinking it, but I believe you'd also have to work around SELinux contexts on the folder and symlink. I've heard of people even having issues after that, so I wouldn't consider it "official" support. Here's an open issue thread about it

Is this new, or has it been happening for a few days/weeks? I'm on Fedora Atomic (which Bazzite is based on) and have never experienced this (though I mostly use Mullvad browser, a fork of Firefox). I tried Bazzite a few weeks ago and also never experienced this with the Firefox flatpak. If it's been happening for awhile, it may be hardware-specific or a config thing. Out of curiosity (just to get a 1:1 comparison), do you experience the same thing with the Mullvad browser flatpak?

Not that I know of? I'm not sure where to even find that information if it does exist