unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 62890@debbugs.gnu.org
Subject: bug#62890: StumpWM fails to start - Read only file system
Date: Fri, 28 Jun 2024 21:03:51 -0400	[thread overview]
Message-ID: <87ed8gv9u0.fsf@freakingpenguin.com> (raw)
In-Reply-To: <877ceewodw.fsf@kitej> (Guillaume Le Vaillant's message of "Mon,  24 Jun 2024 11:50:35 +0000")

Hi Guillaume,

Thanks, your patch works for me! I don't expect many use cases to break
from this (how many people want to install stumpwm lib but not stumpwm
proper), but there's probably a fair amount of configs that'll break.
Maybe it deserves a NEWS entry.

I dream of the day https://issues.guix.gnu.org/48907 is fixed.

While testing this I noticed that the error message can be even less
descriptive than reported previously. With my current StumpWM config,
without your patch, and with grafts enabled I get the following error:

> Memory fault in 0x<some_random_hex_address>.

Yeah, that's a fun one to debug. Very informative 🙂. I spent far too
long bisecting a big Guix commit list before realizing this was ALSO a
grafting issue.

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.




  reply	other threads:[~2024-06-29  1:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 22:32 bug#62890: StumpWM fails to start - Read only file system Kjartan Óli Águstsson
2023-04-24 12:57 ` Guillaume Le Vaillant
2023-04-25  9:35   ` Guillaume Le Vaillant
2024-01-12 21:02 ` bug#62890: StumpWM with --no-grafts and System/Home mismatches Richard Sent
2024-05-03  2:30 ` bug#62890: Specific graft that's at fault Richard Sent
2024-05-27  6:54 ` bug#62890: Likely cause found, excess library grafting Richard Sent
2024-05-27  7:05   ` bug#62890: StumpWM fails to start - Read only file system Richard Sent
2024-06-24 11:50     ` Guillaume Le Vaillant
2024-06-29  1:03       ` Richard Sent [this message]
2024-06-29  9:03         ` Guillaume Le Vaillant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed8gv9u0.fsf@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=62890@debbugs.gnu.org \
    --cc=glv@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).