StumpWM fails to start - Read only file system

  • Open
  • quality assurance status badge
Details
3 participants
  • Guillaume Le Vaillant
  • Kjartan Óli Águstsson
  • Richard Sent
Owner
unassigned
Submitted by
Kjartan Óli Águstsson
Severity
normal
K
K
Kjartan Óli Águstsson wrote on 17 Apr 2023 00:32
(address . bug-guix@gnu.org)
GV1P193MB23106F1D18FD3516594772CBDF9F9@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM
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
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
branch: master
commit: 9a5e1dc1f16f5f8c056e64f2077b035784003673
but I tried rolling back to an earlier system generation:
guix:
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.

--
Kjartan Oli Agustsson
GPG Key fingerprint: 4801 0D71 49C0 1DD6 E5FD 6AC9 D757 2FE3 605E E6B0
-----BEGIN PGP SIGNATURE-----

iQHLBAEBCAA1FiEESAENcUnAHdbl/WrJ11cv42Be5rAFAmQ8e5UXHGtqYXJ0YW5v
bGlAb3V0bG9vay5jb20ACgkQ11cv42Be5rBssgv+MZWF74qgxhIe3tm5ALAWNdQB
9+B+neLCrO6yiujo343lthpPM6FgeSVJ0vpMZnE1gDCX9pg45iWU/d3MIHNSIeEC
cIKPXIZHbwQWPQBqPA0lEGshOa9PGBCGrs7XuqyvPmRaEvKcTnNx/Vs+qRNOdR6T
f4dPDgb6Y7CpPIcC84DiV9eg4I+W3XlS2xePnnqgSBgbvAU86yYpbjMSVE2O/InI
8PNRKnp5XPvsNuDHVzi/79g2FXMEfTQKGlyeWZqdsv4KMj+3Xze/3LCHihl67gEd
9kzFaAKxFlNQTn0aK9fBthEC0eK3HGu5vCf+QjoBayAFAXhYBBcWSue/cRlVUohY
xk1knjXFLUZbkWZ4l7Oa+6e3DWEcYmMdJmM2kC/NIyO9fxVmLK6uWyU2X/l1HVCh
CRYPXSU7bgdVC9iDEbBkmrLIqE342vjvOj6gANTt7r4w6tEXvS2G9j6qCgVQdlW/
sF7TrNCulIoLqaixaFYbESAi2mPGOH22CpAjAO+r
=7+6W
-----END PGP SIGNATURE-----


G
G
Guillaume Le Vaillant wrote on 24 Apr 2023 14:57
(name . Kjartan Óli Águstsson)(address . kjartanoli@outlook.com)(address . 62890@debbugs.gnu.org)
878rehifo4.fsf@kitej
Kjartan Óli Águstsson <kjartanoli@outlook.com> skribis:

Toggle quote (24 lines)
> 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...
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCZEaBKw8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9SdgD9G+NN54TQ5dXqN+Qu+vT2amTOGrLziC5gmsJJ
m7w45WgA/jfK4NFpi+lJPvcJfeF84hdiE94Zd0XCwZDYJCKwL3oM
=EDnO
-----END PGP SIGNATURE-----

G
G
Guillaume Le Vaillant wrote on 25 Apr 2023 11:35
(name . Guillaume Le Vaillant)(address . glv@posteo.net)
877cu05ltz.fsf@kitej
I think the issue comes from grafts.

Without grafts, the ASDF configuration is coherent; the path for
stumpwm's sources and libraries is the same everywhere (here in
stumpwm:lib and sbcl-stumpwm-cpu):

Toggle snippet (22 lines)
$ cat $(guix build --no-grafts stumpwm | grep 'lib$')/etc/common-lisp/*/50-stumpwm.conf
(("/gnu/store/v18hzbid3rjblz35s69w4c0gcsx9f9w9-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm"
:**/
:*.*.*)
("/gnu/store/v18hzbid3rjblz35s69w4c0gcsx9f9w9-stumpwm-22.11-lib/lib/common-lisp/sbcl/stumpwm"
:**/
:*.*.*))

(:tree "/gnu/store/v18hzbid3rjblz35s69w4c0gcsx9f9w9-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm")

$ cat $(guix build --no-grafts sbcl-stumpwm-cpu)/etc/common-lisp/*/50-stumpwm.conf
(("/gnu/store/v18hzbid3rjblz35s69w4c0gcsx9f9w9-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm"
:**/
:*.*.*)
("/gnu/store/v18hzbid3rjblz35s69w4c0gcsx9f9w9-stumpwm-22.11-lib/lib/common-lisp/sbcl/stumpwm"
:**/
:*.*.*))

(:tree "/gnu/store/v18hzbid3rjblz35s69w4c0gcsx9f9w9-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm")


With grafts, we get different paths, which probably explains why ASDF
fails to find the compiled Lisp files it is looking for:

Toggle snippet (20 lines)
$ cat $(guix build stumpwm | grep 'lib$')/etc/common-lisp/*/50-stumpwm.conf
(("/gnu/store/wsjyjqf20ldbmgdq96h73qikmwhxv36c-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm"
:**/
:*.*.*)
("/gnu/store/wsjyjqf20ldbmgdq96h73qikmwhxv36c-stumpwm-22.11-lib/lib/common-lisp/sbcl/stumpwm"
:**/
:*.*.*))

(:tree "/gnu/store/wsjyjqf20ldbmgdq96h73qikmwhxv36c-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm")

$ cat $(guix build sbcl-stumpwm-cpu)/etc/common-lisp/*/50-stumpwm.conf
(("/gnu/store/h8i8mwsgjb96r407xqa2sf56clgy7r7c-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm"
:**/
:*.*.*)
("/gnu/store/h8i8mwsgjb96r407xqa2sf56clgy7r7c-stumpwm-22.11-lib/lib/common-lisp/sbcl/stumpwm"
:**/
:*.*.*))

(:tree "/gnu/store/h8i8mwsgjb96r407xqa2sf56clgy7r7c-stumpwm-22.11-lib/share/common-lisp/sbcl/stumpwm")
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCZEejOA8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j8JWAD/XbO6V2+ZOWww6M1/AJJ3meeCnG0lSZFIJspj
72/m7lAA/RSLVnm64CbDerB5H65zC2INTyOHO3vnEEtcbvDUZe7A
=Uiaz
-----END PGP SIGNATURE-----

R
R
Richard Sent wrote on 12 Jan 22:02 +0100
StumpWM with --no-grafts and System/Home mismatches
(address . 62890@debbugs.gnu.org)
1e0e77cc4d8f9b49c181d8eff6ee2bdd@freakingpenguin.com
I've noticed the same behavior and was able to resolve it by adding
--no-grafts whenever I reconfigure my system and home profiles. Likely
just the former is necessary, but I haven't tested it.

I've also noticed this behavior (SBCL trying to place .fasl in
/gnu/store) once when I pulled, reconfigured system, and didn't
reconfigure home. I have my setup configured such that StumpWM is
installed at the system level, while contrib packages are installed via
guix home.

I ran a git bisect and continually reconfigured my system to try and
narrow down what commit it was, and was able to isolate it to either an
xorgproto or Mesa update. Home was built before (49a7a95ba4) the commit,
System after (d55a4431f3). The offending commit in this particular case
lies somewhere between d55a4431f3 and 17c3a3bfff. (This probably isn't
actually a bug, but I'm posting it in case anyone else runs into a
similar issue in the future.)

If anyone else has a similar setup, encounters this issue, and already
uses --no-grafts, be sure both the system and home profiles are built
with the same version of Guix.

Richard Sent
?