unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Timothy Sample <samplet@ngyro.com>
Cc: 51992-done@debbugs.gnu.org
Subject: bug#51992: [PATCH core-updates-frozen] gnu: gnome-session: Restore elogind support.
Date: Sun, 21 Nov 2021 09:13:39 -0500	[thread overview]
Message-ID: <87v90lbnqk.fsf@gmail.com> (raw)
In-Reply-To: <87wnl3e9wj.fsf@ngyro.com> (Timothy Sample's message of "Fri, 19 Nov 2021 23:19:40 -0500")

Timothy Sample <samplet@ngyro.com> writes:

> Hi all,
>
> Here’s a fix for another breakdown in communication between GNOME and
> elogind.  With this patch, I can power down my machine from GDM.  The
> gnome-session patch comes from Gentoo.  On one hand, it’s not perfect.
> It sets the “HAVE_SYSTEMD” flag, causing gnome-session to try and talk
> to systemd for things that have nothing to do with logind.  On the other
> hand, this isn’t a regression for us.  It’s essentially how we did it
> before (if you run GDM or GNOME, check your logs: gnome-session is
> complaining about systemd).
>
>>From 443a14f9c3eb400a5093dad2758bd0f3cc68e457 Mon Sep 17 00:00:00 2001
> From: Timothy Sample <samplet@ngyro.com>
> Date: Fri, 19 Nov 2021 20:29:57 -0500
> Subject: [PATCH] gnu: gnome-session: Restore elogind support.
>
> * gnu/packages/patches/gnome-session-support-elogind.patch: New file.
> * gnu/local.mk: Add it.
> * gnu/packages/gnome.scm (gnome-session)[source]: Use it.
> [arguments]: Add "-Delogind=true" to #:configure-flags; remove
> phases that patch in old-style elogind support.
> ---
>  gnu/local.mk                                  |  1 +
>  gnu/packages/gnome.scm                        | 14 +---

Applied, thank you!

Maxim




      reply	other threads:[~2021-11-21 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20  4:19 [bug#51992] [PATCH core-updates-frozen] gnu: gnome-session: Restore elogind support Timothy Sample
2021-11-21 14:13 ` Maxim Cournoyer [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

  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=87v90lbnqk.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=51992-done@debbugs.gnu.org \
    --cc=samplet@ngyro.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).