From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: contact.ng0@cryptolab.net, 26283-done@debbugs.gnu.org
Subject: bug#26283: xfce: lid close does not suspend system
Date: Wed, 24 Mar 2021 23:03:18 +0100 [thread overview]
Message-ID: <86y2ec9pll.fsf@gmail.com> (raw)
In-Reply-To: <86ft37tyxx.fsf@gmail.com> (zimoun's message of "Mon, 11 Jan 2021 13:55:54 +0100")
Hi,
On Mon, 11 Jan 2021 at 13:55, zimoun <zimon.toutoune@gmail.com> wrote:
> On Fri, 18 Dec 2020 at 22:53, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>> zimoun 写道：
>>> On Tue, 28 Mar 2017 at 17:52, ng0 <contact.ng0@cryptolab.net> wrote:
>>>> With xfce4 on GuixSD, closing a laptop's lid does not suspend the
>>>> system. It just locks the screen.
>>>
>>> After this oneline comment, if someone using xfce4 could provide
>>> moreinfo. Otherwise, I will close this bug after the usual 3 weeks
>>> delay.
>>
>> Specifically, we'd need to know whether the laptop was on mains (no suspension
>> expected unless XFCE overrides defaults) or battery power, and any relevant
>> settings. Unlikely news from 2017.
>
> Because this bug needs moreinfo and the submitter clearly stated that
> they will not do [1], then I am proposing to close…
>
>> But who knows:
>> <https://lists.gnu.org/archive/html/help-guix/2020-12/msg00147.html>
>> might be this very bug from beyond the grave.
>
> …or track the bug here. :-) If it is the same bug, the title of this
> report should be changed; maybe it is not XFCE only related.
>
> 1: <http://logs.guix.gnu.org/guix/2020-12-01.log#235356>
After waiting for 10 weeks for moreinfo for a bug from 2017, I am
closing.
All the best,
simon
prev parent reply other threads:[~2021-03-24 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 17:52 bug#26283: xfce: lid close does not suspend system ng0
2020-12-18 20:03 ` zimoun
2020-12-18 21:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-01-11 12:55 ` zimoun
2021-03-24 22:03 ` zimoun [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=86y2ec9pll.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=26283-done@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
--cc=me@tobias.gr \
/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).