this post was submitted on 31 Mar 2026
6 points (80.0% liked)
Linux
64383 readers
345 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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-releaseIf
terra-releaseis layered^[You can check this withrpm-ostree status. If it is, you will find it afterLayeredPackages:. If it's not, you should not evokerpm-ostree uninstall terra-release, as it wouldn't get through anyways.], then we'd have to start withrpm-ostree uninstall terra-release. Afterwards, to delete the Terra repository, even if it's not even there^[Ifls /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-releaseTo (re)install
terra-release(as per its own instructions):First evoke the following command:
And then, evoke this one:
sudo rpm-ostree install terra-release. I'm unsure ifsudois required. Personally, first I'll do is withoutsudo. Only after it fails due to permissions will I do it withsudo.A reboot is probably required for it to take effect. Hence, try evoking
rpm-ostree install throneonly after performing a reboot.Alrightie, this worked! I did install Throne. As per
sudobeforerpm-ostree- it's not necessary, it just asks for su password if you run it without sudo.So, Throne came up with another error, it was unable to change file ownership in /usr directory (of course it couldn't, it's an immutable system)...and then it got me.
I read into the errors given by v2rayN, and checked it on a regular mutable distro...and indeed, my subscription list got blocked right when I started testing TUN on Bazzite a few days ago. Case closed, Bazzite has nothing to do with it.
But, I learned something about Bazzite repo management, which will be valuable going forward. Thanks a lot for so much effort figuring things out!
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.
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).
😅. This is actually a very nuanced topic:
/usrcompared 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./usr/etc,/usr/shareet cetera; one could instead make changes to the content of folders like/etc~/.local/shareet cetera./usronce and would like for said changes to not persist after a reboot, then commands likerpm-ostree usroverlayandbootc usr-overlayare worth mentioning.So, to be clear: while it is true that Fedora Atomic does not like/support making changes to
/usrat runtime, it's not like it's necessarily limiting you if you really desire to do so.It has been my pleasure 😊!