unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@posteo.net>
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 19:44:27 -0500	[thread overview]
Message-ID: <87a7g8qq38.fsf@posteo.net> (raw)
In-Reply-To: <87y33spr33.fsf@ngyro.com>


Timothy Sample writes:

> Hi Brett,
>
> brettg@posteo.net writes:
>
>> On 29.04.2019 18:05, Timothy Sample wrote:
>>>
>>> After doing some testing in a VM, it looks like this is an issue
>>> with my
>>> recent commit: 8caa458953eeac783c73a0e5aaa72842fe3914c9.
>>>
>>> I added a placeholder desktop entry file, and even though I did my best
>>> to make it invisible, GDM is still selecting it.  (I tested GNOME and
>>> XFCE, but I guess they were preferred by GDM over the placeholder,
>>> whereas StumpWM is not.  Maybe the has to do with how the names are
>>> sorted.)
>
> This is exactly the problem.  To find a default session, it sorts the
> names of all the “.desktop” files it can find (using “g_strcmp0”), and
> picks the first.  Since we have “GNOME” < “XFCE” < “Fail” < “stumpwm”,
> my tests did not catch this error.
>
> 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).
>
>
> In the future, we should find a way to make GDM errors less
> catastrophic, but I doubt we could do that in a day (I certainly
> couldn’t)!
>
>> Thank you for looking into this Tim! I have gone back to SLiM for the
>> time being until it is fixed :).
>>
>> If anybody else is having this issue, going back to SLiM is really
>> easy, check out my commit for reference.
>>
>> https://github.com/brettgilio/guix-system/commit/64d389db13c2f78ee5c58af28c1639b098113c93
>
> Thanks for providing this.  Hopefully it helps anybody else having
> problems.
>
>
> -- Tim

I think the uglier version is more generic and less likely to cause
future errors. But, it is a matter of time. The uglier one is likely
going to be more terse.

Do you need any help on my end?

Brett Gilio

  parent reply	other threads:[~2019-04-30  0:45 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
2019-04-30  3:10           ` Timothy Sample
2019-04-30 12:46             ` Ludovic Courtès
2019-04-30  0:44         ` Brett Gilio [this message]
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

  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=87a7g8qq38.fsf@posteo.net \
    --to=brettg@posteo.net \
    --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 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).