From: 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:20:53 +0200 [thread overview]
Message-ID: <31a3e9cda50ae26c7771c104fdbf97bb@posteo.net> (raw)
In-Reply-To: <87d0l4re46.fsf@ngyro.com>
On 29.04.2019 18:05, Timothy Sample wrote:
> Hi again,
>
> Timothy Sample <samplet@ngyro.com> writes:
>
>> Hi Brett,
>>
>> Brett Gilio <brettg@posteo.net> writes:
>>
>>> Hey all
>>>
>>> I just reconfigured my system configuration after the big staging
>>> merge
>>> to master. I use StumpWM.
>>>
>>> GDM seems to be starting just fine, but after this reconfiguration
>>> stumpwm or X or something is crashing for me and looping me back to
>>> GDM.
>>>
>>> Where are the logs I can view for this? I see some message appear but
>>> quickly disappear before looping back into GDM.
>>
>> GDM logs things to “/var/log/messages”. However, it may not be useful
>> in this case (do take a look, though).
>>
>>> If I can get the logs I can share them or try and figure it out
>>> myself.
>>
>> You could also share some other details about your config. For
>> instance, how is StumpWM started? Do you have a “~/.xsession” script
>> or
>> does StumpWM provide a “.desktop” file that GDM needs to find?
>
> 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.) I will try and fix this today, but in the mean time, you can
> either:
>
> • go back to using SLiM for now;
> • launch StumpWM from “~/.xsession”; or
> • install another WM, so that you can select StumpWM explicitly
> when
> logging in (using the little gear icon that shows up when you
> have
> multiple sessions available).
>
> Sorry!
>
>
> -- Tim
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
next prev parent reply other threads:[~2019-04-29 17:22 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 [this message]
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
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=31a3e9cda50ae26c7771c104fdbf97bb@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).