From: Timothy Sample <samplet@ngyro.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, Rene <pacoon@protonmail.com>
Subject: Re: GNOME 3.30: help needed!
Date: Wed, 09 Jan 2019 13:52:00 -0500 [thread overview]
Message-ID: <87wondeka7.fsf@ngyro.com> (raw)
In-Reply-To: <87o98plv5b.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 09 Jan 2019 16:15:28 +0100")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> [...]
>
> Now the only remaining question is: what files on my system cause this
> failure to start GNOME? I’ll be playing with this some more and hope to
> identify the files that are responsible, so that we can either work
> around this or document it.
Currently, GDM is configured to log all debug messages. It creates a
“/var/log/gdm” folder, but ignore that! All the juicy bits end up in
“/var/log/debug”. It is usually pretty clear about what’s going on. If
not, feel free to send along any relevant messages and I’ll weigh in as
best I can.
-- Tim
next prev parent reply other threads:[~2019-01-09 18:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 6:13 GNOME 3.30: help needed! Rene
2019-01-04 8:06 ` Ricardo Wurmus
2019-01-04 11:44 ` Catonano
2019-01-04 11:52 ` Catonano
2019-01-04 12:45 ` Catonano
2019-01-05 4:43 ` Rene
2019-01-05 4:37 ` Rene
2019-01-07 12:18 ` Ricardo Wurmus
2019-01-07 23:55 ` Rene
2019-01-09 14:08 ` Ricardo Wurmus
2019-01-09 15:15 ` Ricardo Wurmus
2019-01-09 18:52 ` Timothy Sample [this message]
2019-01-09 19:42 ` Ricardo Wurmus
2019-01-11 9:49 ` how to fix state-broken affected user services? (Re: GNOME 3.30: help needed!) Giovanni Biscuolo
2019-01-11 10:04 ` Ricardo Wurmus
2019-01-11 10:46 ` Giovanni Biscuolo
2019-01-11 11:41 ` Ricardo Wurmus
2019-01-14 15:17 ` GNOME 3.30: help needed! L p R n d n
-- strict thread matches above, loose matches on Subject: below --
2018-12-21 19:43 Ricardo Wurmus
2018-12-23 13:59 ` L p R n d n
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wondeka7.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=pacoon@protonmail.com \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.