unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Luther Thompson <lutheroto@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35175@debbugs.gnu.org
Subject: bug#35175: Cannot reconfigure
Date: Mon, 8 Apr 2019 19:27:52 -0400	[thread overview]
Message-ID: <20190408192752.769b66fe@gmail.com> (raw)
In-Reply-To: <20190408125414.2b023d08@scratchpost.org>

On Mon, 8 Apr 2019 12:54:14 +0200
Danny Milosavljevic <dannym@scratchpost.org> wrote:

> The reason for the error Luther encountered is because something is
> up with the gdm service.
> 
> And that's because of
> 
>                       (extend params (compose extensions)))
> 
> And I guess the extension/composition mechanism of gdm is broken.
> 
> There was a commit
> 
> commit 0cf981a6066711f6e830a3f1d40f7c265b0bac94
> Author: Ludovic Courtès <ludo@gnu.org>
> Date:   Fri Apr 5 17:40:01 2019 +0200
> 
>     services: gdm: Properly handle empty extensions lists.
> 
> recently.
> 
> @Luther: Could you try with the commit right before that change?

I think that's the commit that *fixed* the problem. It didn't work for
me until 2 days later, which may be due to the fact that `guix system
reconfigure` actually installs a system from a couple of `guix pull`s
ago. I know that by seeing the Linux versions in GRUB.

Luther

  parent reply	other threads:[~2019-04-08 23:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06 19:34 bug#35175: Cannot reconfigure Luther Thompson
2019-04-06 20:44 ` znavko
2019-04-06 21:26   ` Luther Thompson
2019-04-07  8:15   ` znavko
2019-04-07 11:02     ` Luther Thompson
2019-04-08 10:54   ` Danny Milosavljevic
2019-04-08 14:46     ` Ludovic Courtès
2019-04-08 23:27     ` Luther Thompson [this message]
2019-04-07 16:25 ` Ludovic Courtès
2019-04-07 21:27   ` Luther Thompson

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=20190408192752.769b66fe@gmail.com \
    --to=lutheroto@gmail.com \
    --cc=35175@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    /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).