Closed wiiznokes closed 1 year ago
I had the same "read-only filesystem" issue on PopOS 22.04
and this seems to be the cause: freedesktop systemd-sysext
System extension images are strictly read-only, and the host /usr/ and /opt/ hierarchies become read-only too while they are activated.
Disabling systemd-sysext
should fix the issue, which will also disable your cosmic-epoch
build.
edit: this will also disable any other systemd-sysext
extensions
sudo systemctl disable systemd-sysext
thanks, that works :pray: . I will add sudo systemctl stop systemd-sysext
if someone will have the same issue
The systemd-extension installation method is meant as an easy way to test the desktop, while proper packaging is not available, without modifying your system. It is not meant as a permanent installation method (at least not on normal mutable installations, on read-only systems like silverblue this is more feasible).
Feel free to submit a PR highlighting this in the README and explaining the effects.
After building the DE on Fedora, i feel like it messed up my install. I post an issue on Fedora forum already https://discussion.fedoraproject.org/t/why-i-have-no-more-disk-space-in-usr/89997 but they redirect me here.
basically, i can't install package because
/usr
is full (but it say it fill at 1%), and/usr
is in read-only.I executed
sudo setenforce 0
and reseted it to 1.gdm package is not installed.
If you have an idea on how can i repair my install, please let me know :pray: