[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#62890: StumpWM fails to start - Read only file system
From: |
Guillaume Le Vaillant |
Subject: |
bug#62890: StumpWM fails to start - Read only file system |
Date: |
Mon, 24 Apr 2023 12:57:46 +0000 |
Kjartan Óli Águstsson <kjartanoli@outlook.com> skribis:
> I just started experiencing an issue with stumpwm where it fails to
> start, complaining about a read only file system. A web search for the
> error message leads me to
> https://lists.gnu.org/archive/html/help-guix/2021-02/msg00080.html,
> which sounds exactly like the problem I'm experiencing. I'm unsure how
> to get the backtrace shared in that thread, or in general how to proceed
> with debugging this.
>
> guix describe shows:
> guix 9a5e1dc
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 9a5e1dc1f16f5f8c056e64f2077b035784003673
> but I tried rolling back to an earlier system generation:
> guix:
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: d513ba83ebca347164098bb0fa1354f3657bc7e2
> to no success so I doubt it is a new change in Guix.
>
> Unless I'm missing something in the help-guix thread there is no
> solution discussed there, so any help in debugging this would be greatly
> appreciated.
Hi,
I just got the same problem after reconfiguring a machine (using
guix-home, but I'm not sure if it is relevant). It only happens when
I try to load extra modules from the ".stumpwm/init.lisp" file.
It looks like the configuration indicating where to search for the
compiled Common Lisp files (ASDF's source-registry and
output-translations) is not taken into consideration by Stumpwm
anymore... so it tries to recompile them in the wrong place.
As a workaround, replacing:
exec stumpwm
by:
exec sbcl --no-userinit --non-interactive --eval '(require :asdf)' --eval
'(asdf:load-system "stumpwm")' --eval '(stumpwm:stumpwm)'
in my ".xsession" file seems to work...
signature.asc
Description: PGP signature