Upvoted for Topgrade. It's honestly so good on any system that employs more than one 'updatable microcosm',

That's definitely off-putting. Though, I do feel Debian can learn a thing or two for making major release updates more seamless. Perhaps it's the doing of the law of equivalent exchange; after two^[You can definitely use it longer, though two years feels like the sweet spot.] years of bliss (read: easy updates), we just have to accept a brief moment of intense suffering (read: way more involved update).

AFAIK Cinnamon is on track to be the first smaller DE with full wayland support.

I think Budgie just beat them to it. To be clear, Budgie 10.10 is literally Wayland-only.

Are you on systemd or sysVinit? If you're on the latter, could you tell if you've even noticed any difference so far? Thanks in advance!

DOOM Emacs

NVChad

You might be the first person I've found on Lemmy that actively uses both DOOM Emacs and a Neovim distribution. Could you perhaps do a deeper dive on your work flow? Thanks in advance!

As I suppose the other user already went over your main query, I'll instead focus on what might have felt rather innocuous.

my default shell is fish

I subscribe to the school of thought that one should not change their default shell^[I suppose it could be fine~ish as long as it's POSIX compliant AND compatible with bash. Which, unfortunately, fish happens to be neither of the two.] through invoking chsh (or whatever other method that applies changes to /etc/passwd). This article does an excellent job at laying down the reasoning (and the recommended alternative). FWIW, the alternative's day-to-day experience provides all of the pros without any of the cons.

fish - Ever since I've made the switch to Linux, the terminal has been part of the experience. And, honestly, I wouldn't want it any other way. Besides its efficiency, I also very much enjoy how it automatically keeps track of everything I do within. I don't get that functionality whenever I do something within a GUI. But bash left a lot to be desired in that regard; its history simply didn't record everything. It was also pretty bare-bones; no syntax highlighting, no auto suggestions etc. Thus, after trying to bend bash (and later zsh) to my will and ultimately being dissatisfied with the janky mess I was left with, I finally gave in to at least give fish a honest try. The rest is history. Heck, fish is the very first thing I install on a machine.

That's pretty cool! Where did you find it?

Great write-up! Thank you for the effort!

Though, if I may: Regarding GNOME, you said:

Not particularly customisable

I would rather rephrase this to "Does not expose many knobs for customization by default.". Because -frankly- between dconf, extensions and CSS; the possibilities are actually quite expansive. So much so, even, that a KDE dev said regarding GNOME: "sometimes it (read: GNOME) can be customized better than KDE". (They say this literally in the first 10 seconds or so.)

Another striking example of the breadth of GNOME's customization would be how Niri was heavily inspired by GNOME's PaperWM extension. (Source) So, GNOME's customizability has allowed the creation of a new workflow that eventually served as a direct inspiration for one of the most exciting WMs we've got.

Do you mean Desktop Environments?

EDIT: OP has changed the title of the post since. Regardless, thank you OP for the confirmation/clarification! FWIW, I really like Eylenburg's resource on this.

I'm glad to hear that you found the most egregious culprit. Hopefully you'll be able to get it to work after your subscription list 'functions' (again). (I'm honestly completely oblivious of what this software is or how it works.)

Though, if you allow me, I would like to give some comments. So, without further ado.

Throne came up with another error, it was unable to change file ownership in /usr directory

Hmm..., curious. I would think that it shouldn't even (necessarily) require anything like that. And, if it does, perhaps the maintainer/contributor should be addressed in hopes of resolving the issue; I'm sure they can figure out a workaround (or so).

(of course it couldn’t, it’s an immutable system)

😅. This is actually a very nuanced topic:

• Bazzite has for example made plenty of changes to /usr compared to its upstream; i.e. Fedora Atomic. So, there is a supported way of doing this in order to create an image with the desired changes to /usr. If you got any such needs, consider taking a look at this page of Bazzite's documentation.
• Furthermore, instead of making changes to the content of folders like /usr/etc, /usr/share et cetera; one could instead make changes to the content of folders like /etc ~/.local/share et cetera.
• If you only want to write to /usr once and would like for said changes to not persist after a reboot, then commands like rpm-ostree usroverlay and bootc usr-overlay are worth mentioning.

So, to be clear: while it is true that Fedora Atomic does not like/support making changes to /usr at runtime, it's not like it's necessarily limiting you if you really desire to make changes to /usr. Even if non of the methods 100% function like how sudo <input change> /usr/<some content> would on a traditional distro*.

Thanks a lot for so much effort figuring things out!

It has been my pleasure 😊!

Bazzite shows that terra-release is indeed installed

Assuming it is disabled (as happened in https://github.com/ublue-os/bazzite/issues/2580)

Interesting conflict; as these seem to be at odds with each other. I wonder what's up. If it's indeed disabled, then I would like to apologize for causing any confusion. FWIW, I may have been mislead by Terra's own documentation. I suppose it might be outdated.

Anyhow, perhaps we can undertake the steps to uninstall terra-release (even if it's not there) and (re)install it.

Uninstalling terra-release

If terra-release is layered^[You can check this with rpm-ostree status. If it is, you will find it after LayeredPackages:. If it's not, you should not evoke rpm-ostree uninstall terra-release, as it wouldn't get through anyways.], then we'd have to start with rpm-ostree uninstall terra-release. Afterwards, to delete the Terra repository, even if it's not even there^[If ls /etc/yum.repos.d/ | grep "terra" doesn't yield anything, then you may skip this. But evoking the command to delete something that's not there, isn't bad or anything.]: sudo rm -rf /etc/yum.repos.d/terra.repo

(Re)installing terra-release

To (re)install terra-release (as per its own instructions):

First evoke the following command:

curl -fsSL https://github.com/terrapkg/subatomic-repos/raw/main/terra.repo | pkexec tee /etc/yum.repos.d/terra.repo

And then, evoke this one: sudo rpm-ostree install terra-release . I'm unsure if sudo is required. Personally, first I'll do is without sudo. Only after it fails due to permissions will I do it with sudo.

A reboot is probably required for it to take effect. Hence, try evoking rpm-ostree install throne only after performing a reboot.