all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>,
	Josh Wheeler <joshwheeler@mantlepro.com>,
	36519@debbugs.gnu.org
Subject: bug#36519: System frequently suspending after logout
Date: Tue, 12 Nov 2019 15:12:01 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1911121336170.11560@marsh.hcoop.net> (raw)
In-Reply-To: <87woc51zul.fsf@gmail.com>

On Mon, 11 Nov 2019, Chris Marusich wrote:

> Josh Wheeler <joshwheeler@mantlepro.com> writes:
>
>> Problem: GuixSD frequently suspends on user logout or after selecting
>> "Log in as another user" from the lock screen.
>>
>> Occurs when returning to GDM from GNOME and i3 sessions on a fresh
>> GuixSD install.
>>
>> Expected: System should allow user logout / switching without sleeping.
>>
>> Thanks!
>
> Could this issue actually be the same issue that is described in the
> following email thread?
>
> "Who is sending my Guix System to sleep?"
> https://lists.gnu.org/archive/html/help-guix/2019-09/msg00172.html
> https://lists.gnu.org/archive/html/help-guix/2019-10/msg00213.html
>
> In the second email, Jack Hill describes a potential work-around.  I
> wonder if it might also work for the issue described in this bug report?

It seems like a slightly different issue. At least, I don't remember 
running into this. However, it seems reasonable to use the 
sleep-inactive-ac-type dconf setting as I describe to see if it helps with 
this behavior as well. Suspend-on-logout may also be controlled by a 
different dconf setting.

I'm not sure how helpful that was, but I did want to reply.

Best,
Jack

      reply	other threads:[~2019-11-12 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 21:25 bug#36519: System frequently suspending after logout Josh Wheeler
2019-11-12  4:29 ` Chris Marusich
2019-11-12 20:12   ` Jack Hill [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=alpine.DEB.2.20.1911121336170.11560@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=36519@debbugs.gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=joshwheeler@mantlepro.com \
    --cc=mail@ambrevar.xyz \
    /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.