From: Timothy Sample <samplet@ngyro.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Peter Baumgarten <me@peterbaumgarten.com>, help-guix <help-guix@gnu.org>
Subject: Re: Lock screen gnome
Date: Thu, 20 Dec 2018 09:48:56 -0500 [thread overview]
Message-ID: <87tvj8b6ef.fsf@ngyro.com> (raw)
In-Reply-To: <CAE4v=phXb_8--x55eDmn1L9a1dvScMeeZQriCB+jw7+j0LALPA@mail.gmail.com> ("Gábor Boskovits"'s message of "Wed, 19 Dec 2018 20:43:02 +0100")
Hi Ludo and Gábor,
Gábor Boskovits <boskovits@gmail.com> writes:
> Hello,
>
> Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2018. dec. 19., Sze, 14:53):
>>
>> Hi Timothy,
>>
>> Timothy Sample <samplet@ngyro.com> skribis:
>>
>> > Someday I would like to return to fixing GDM, but I am a bit
>> > traumatized. It is a very slow and frustrating package to debug.
>> >
>> > 1. https://lists.gnu.org/archive/html/guix-devel/2017-08/msg00268.html
>> > https://lists.gnu.org/archive/html/guix-devel/2017-10/msg00231.html
>>
>> I would love to have GDM fixed for 1.0 though, because this GNOME
>> screen-locking issue, among other things, is really problematic.
>>
>> Is there anything we can do to help or otherwise provide motivation?
>> :-)
>>
>> Thanks,
>> Ludo’.
>>
>
> Yes, I also believe we need this. Along with the screen-locking
> multi-monitor support and i18n support comes to mind.
>
> If we can help in any way, please feel free to contact us.
>
> Thanks,
> g_bor
The way I was testing it was by running it in a VM. This made testing
any little idea take way too long. It would be nice to have a faster
way of testing it. If anyone has any experience running a nested
instance of GDM, being able to do that would be a big help. (The trade
off is that figuring that out might be just as hard as fixing GDM in the
first place.)
Other than that, I agree that this is a critical feature. GNOME needs
GDM to work smoothly, and GNOME is pretty important for wider adoption.
I am happy to take another look at this (eventually!), but I do not have
any particular expertise here, so if anyone else is feeling brave, they
would have just as good a chance at fixing it as me. :)
-- Tim
prev parent reply other threads:[~2018-12-20 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 20:20 Lock screen gnome Peter Baumgarten
2018-12-14 22:33 ` Timothy Sample
2018-12-16 5:05 ` Chris Marusich
2018-12-16 17:35 ` Peter Baumgarten
2018-12-19 13:52 ` Ludovic Courtès
2018-12-19 19:43 ` Gábor Boskovits
2018-12-20 14:48 ` Timothy Sample [this message]
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=87tvj8b6ef.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=boskovits@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@peterbaumgarten.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 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.