This appears on login: no write access to $HOME directory if this is intentional set $KDE_HOME_READONLY=1 in your environment
When I try to run pacman I get:
“/var/lib/pacman/sync/core.db.sign” is not readable: No such file or directory
Octopi fails with this error: QIODevice::write (QFile, “usr/lib/octopi/octphelper.log”: device not open
error: failed to init transaction (unable to lock database)
error: could not lock database: Read-only file system
You need to remove that env var.
That variable already has no value. It’s that my system is set read only somehow by an update, not that an env variable exists that’s the problem.
What updated before the issue started:
i2c-tools, lib32-json-c, libelf, lib32-libelf, qca-qt5, qca-qt6, xfsprogs
My file system is btrfs
Solved it. Turns out btrfs will sometimes put the filesystem into read only mode if it encounters an error. I ran : sudo btrfs check and then: sudo btrfs check --repair
It fixed my issue, but make sure you back up when using that command, it can be dangerous to use.