unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: Leo Prikler <leo.prikler@student.tugraz.at>,
	39281@debbugs.gnu.org, sirgazil@zoho.com
Subject: bug#39281: gdm doesn't start
Date: Tue, 28 Jan 2020 05:21:52 +0000	[thread overview]
Message-ID: <7d118f5a9a05204eacd9388cf9578b2a@disroot.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2001271401340.11123@marsh.hcoop.net>

> Indeed, my system does have a really slow disk, so it would not surprise me if that contributed to
> it. Of course that shouldn't matter, but that's the only thing I can think it. It would be nice to
> hear if sirgazil can reproduce the fix since I think they were having the same problem on their
> computer.

I see.

> I agree that fixing is better than removing. Good luck debugging. I'm happy to test, but am
> currently out of ideas.

Cool! I'll keep you posted.

> I'm glad that you took this well :). However, while I'm often sarcastic, I wasn't trying to be
> here. What I was trying to express was that while I'm currently running my system with
> gnome-initial-setup removed doesn't mean that I don't appreciate the change to make it present by
> default. Fortunately for me, Guix makes this easy compared to other systems!

Haha. All good then. :-)

Regards,
RG.

  parent reply	other threads:[~2020-01-28  5:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d65f5a5c54b87c11f535d6b3080e794c21dbedd6.camel@student.tugraz.at>
2020-01-27  2:26 ` bug#39281: gdm doesn't start Jack Hill
2020-01-27  3:30 ` Raghav Gururajan
2020-01-27  4:50   ` Jack Hill
2020-01-27  4:52     ` bug#39281: [PATCH] gnu: gnome: don't propagate gnome-initial-setup Jack Hill
2020-01-27  5:24     ` bug#39281: gdm doesn't start Leo Prikler
2020-01-28  9:37       ` Leo Prikler
2020-01-28 18:03         ` Jack Hill
2020-01-28 18:18           ` sirgazil via Bug reports for GNU Guix
2020-01-28 18:21             ` Jack Hill
2020-01-28 18:26               ` sirgazil via Bug reports for GNU Guix
2020-01-28 20:11         ` Danny Milosavljevic
2020-01-27  8:51   ` Raghav Gururajan
2020-01-27 19:08     ` Jack Hill
2020-01-27 19:54       ` sirgazil via Bug reports for GNU Guix
2020-01-27 20:13         ` Jack Hill
2020-01-27 20:24         ` Danny Milosavljevic
2020-01-27 21:06           ` Jack Hill
2020-01-27 20:29         ` Danny Milosavljevic
2020-01-27 22:07           ` sirgazil via Bug reports for GNU Guix
2020-01-28  5:21     ` Raghav Gururajan [this message]
2020-01-25 20:32 Jack Hill
2020-01-25 22:32 ` sirgazil via Bug reports for GNU Guix
2020-01-26  3:33   ` Jack Hill

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=7d118f5a9a05204eacd9388cf9578b2a@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=39281@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    --cc=leo.prikler@student.tugraz.at \
    --cc=sirgazil@zoho.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).