From: sirgazil via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: raghavgururajan@disroot.org, jackhill@jackhill.us,
leo.prikler@student.tugraz.at, 39281@debbugs.gnu.org
Subject: bug#39281: gdm doesn't start
Date: Mon, 27 Jan 2020 17:07:34 -0500 [thread overview]
Message-ID: <16fe90bacb9.db79669456866.8464002501351461004@zoho.com> (raw)
In-Reply-To: <20200127212905.4955429b@scratchpost.org>
---- On Mon, 27 Jan 2020 15:29:05 -0500 Danny Milosavljevic <dannym@scratchpost.org> wrote ----
> Patch applied to guix master as commit 4fc4e5fdd9da6320aa94eeec61cbb84a7dc9460e
> for now.
>
Problem solved for me :)
next prev parent reply other threads:[~2020-01-27 22:08 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 [this message]
2020-01-28 5:21 ` Raghav Gururajan
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=16fe90bacb9.db79669456866.8464002501351461004@zoho.com \
--to=bug-guix@gnu.org \
--cc=39281@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=jackhill@jackhill.us \
--cc=leo.prikler@student.tugraz.at \
--cc=raghavgururajan@disroot.org \
--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).