From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: Cairn <cairn@pm.me>, 57052@debbugs.gnu.org
Subject: bug#57052: elogind-service specifies a variable that's ignored by defualt
Date: Tue, 09 Aug 2022 09:57:05 -0400 [thread overview]
Message-ID: <87wnbho6z2.fsf@gmail.com> (raw)
In-Reply-To: <8735e5plra.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 09 Aug 2022 09:52:25 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi,
>
> Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
>
>> Am Sonntag, dem 07.08.2022 um 23:29 +0000 schrieb Cairn:
>>> "HandleLidSwitchExternalPower= is completely ignored by default (for
>>> backwards compatibility)"[1]
>>>
>>> I noticed (with help in IRC) that my laptop wasn't suspending on lid
>>> close when plugged in and charging, which I hadn't seen happen on
>>> other systems. I now know that I can set this by configuring the
>>> `elogind-service` parameter `handle-lid-switch-external-power`.
>>> Regardless, it seems like it should default to being unset rather
>>> than set/ignored, since that would heed the line I quoted above.
>> I think you're misreading that line. What it states is not that
>> "HandleLidSwitchExternalPower" is ignored by default, but
>> "HandleLidSwitchExternalPower=" is ignored by default, i.e. there will
>> be no value unless one was provided (whichever semantics "no value" has
>> later on) is only confusingly explained later on.
>>
>> IMHO the Guix behaviour of always setting a value is the right one
>> (explicit is better than implicit after all). As for the default
>> values, one might disagree as to which fits, but I don't think ignoring
>> lid switches while powered is harmful.
>
> It can be. I have a Lenovo T430s with a partially discolored LCD from
> heat after I left it closed in a backpack for a couple hours, thinking
> it would have suspend (it was not). That would not have happened with
> the value supposed to be default (which matches the behavior used on
> most other systems).
>
> So I'd favor having the default to suspend on any lid close.
For the record, this was noticed and discussed more than a year ago, see
Message-ID: <871rens9a2.fsf@nckx>. It had fallen into the cracks, it
seems.
Maxim
next prev parent reply other threads:[~2022-08-09 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 23:29 bug#57052: elogind-service specifies a variable that's ignored by defualt Cairn via Bug reports for GNU Guix
2022-08-08 10:45 ` Liliana Marie Prikler
2022-08-09 1:52 ` bokr
2022-08-09 6:34 ` Liliana Marie Prikler
2022-08-09 6:42 ` Cairn via Bug reports for GNU Guix
2022-08-09 13:52 ` Maxim Cournoyer
2022-08-09 13:57 ` Maxim Cournoyer [this message]
2022-08-09 14:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-09 14:42 ` Cairn via Bug reports for GNU Guix
2022-08-10 4:38 ` Maxim Cournoyer
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=87wnbho6z2.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=57052@debbugs.gnu.org \
--cc=cairn@pm.me \
--cc=liliana.prikler@ist.tugraz.at \
/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).