all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: 35484@debbugs.gnu.org
Subject: bug#35484: GDM failing to start stumpwm after merge
Date: Mon, 29 Apr 2019 23:49:47 +0200	[thread overview]
Message-ID: <87d0l4a3d0.fsf@gnu.org> (raw)
In-Reply-To: <87y33spr33.fsf@ngyro.com> (Timothy Sample's message of "Mon, 29 Apr 2019 15:08:16 -0400")

Hi Tim,

Timothy Sample <samplet@ngyro.com> skribis:

> I can think of two options for a fix before 1.0 (which is supposed to be
> tomorrow!).  The cute one is to just rename “Fail” to “~Fail”, on the
> expectation that this will come after most other names when sorted.  The
> ugly one is to patch GDM to exclude the placeholder file when looking
> for “.desktop” files, and then to select it instead of raising an error
> when it can’t find anything.
>
> My preference is for the ugly one, because the cute one feels like
> putting a silly hack on top of silly hack – it’s just a bit too much.
> I’ve attached a patch.  Thoughts?  (If I don’t hear anything, I will
> push it – it’s important that this works for 1.0).

I don’t have an opinion as I didn’t follow this closely.

Could you make sure the fix works with the DEs and WMs that the
installer proposes (see (gnu installer services))?

If it does, could you push it also to the ‘version-1.0.0’ branch?

Thank you for looking into this!

Ludo’.

  reply	other threads:[~2019-04-29 21:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29  4:30 bug#35484: GDM failing to start stumpwm after merge Brett Gilio
2019-04-29  8:46 ` pelzflorian (Florian Pelz)
2019-04-29 13:16 ` Timothy Sample
2019-04-29 16:05   ` Timothy Sample
2019-04-29 17:20     ` brettg
2019-04-29 19:08       ` Timothy Sample
2019-04-29 21:49         ` Ludovic Courtès [this message]
2019-04-30  3:10           ` Timothy Sample
2019-04-30 12:46             ` Ludovic Courtès
2019-04-30  0:44         ` Brett Gilio
2019-04-30  3:20           ` Timothy Sample
2019-04-29 15:25 ` Ricardo Wurmus

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

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

  git send-email \
    --in-reply-to=87d0l4a3d0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35484@debbugs.gnu.org \
    --cc=samplet@ngyro.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.