Closed Hyzual closed 3 months ago
Same issue on NixOS unstable (both home-manager and system pin: 85f1ba3e51676fa8cc604a3d863d729026a6b8eb)
Same issue on NixOS 23.11 (naturally). Thanks @Hyzual for the workaround. I actually don't understand why ProtectHome=read-only
is there in the service file; doesn't the lorri daemon need to write to ~/.cache/lorri/
? Or does that only ever get written to by the user shell level lorri
commands, e.g. in .envrc
? :thinking:
Fix and more information in nixpkgs PR https://github.com/NixOS/nixpkgs/pull/275024
Describe the bug Ater upgrading to Fedora 39, lorri service fails to start. Here is an extract of
journalctl --user -u lorri.service
It repeats until it reaches the restart counter 5, at which point systemd stops it from restarting.
Workaround:
edit the file at
~/.config/systemd/user/lorri.service
and change it like so:systemctl --user daemon-reload
systemctl --user start lorri.service
The lorri daemon now runs without error.
To Reproduce Steps to reproduce the behavior:
cd
to a repository wherelorri
was init. There is a message stating that the lorri daemon is not started.Expected behavior I expected lorri to function the same way as on Fedora 38.
Metadata
Lorri daemon crashed with
ERRO IO error binding to socket: Read-only file system (os error 30)
Additional context
I don't know what more to include. I don't know what changed between Fedora 38 and 39 that could explain this. I can run more commands to gather context, please ask.