[systemd-devel] logind lid default configuration feedback

[Jiří Procházka]

On 10/03/2012 03:27 PM, Lennart Poettering wrote:
> On Wed, 03.10.12 03:50, Jiří Procházka (ojirio at gmail.com) wrote:
> 
>> Greetings,
>> I'm here to complain about a bad decision to default configuration keys
>> HandleLidSwitch to suspend (instead of ignore) and
>> LidSwitchIgnoreInhibited to yes (instead of no).
>> Many of users use desktop environments handle this action and its
>> configuration (like XFCE in my case). Aside of rather obvious point of
>> overlap of responsibilities, which is a problem rather diplomatical and
>> hard to solve - not point of my call, the problem I have is that
>> Systemd's Logind makes a certain assumption about user wants and forces
>> it down on them. Not everyone wants their laptop to suspend to RAM when
>> the lid is close. After an update of my system (which in this case
>> brought logind on) I expected my system to work at least like it worked
>> before (if not better), respecting my configuration choices, I closed my
>> laptop lid and walked away for an hour or so, I expected it to crunch
>> data, I lost that time due to bad logind default config decision,
>> fortunately not that a big deal, but the principle holds. I hope any new
>> software developments will have more of that respect.
> 
> You can easily change the defaults for your installation. But in general
> we try to find good defaults that work for most people, and we believe
> that suspend-when-closed is a sane policy for this case. I am sorry if
> you disagree but I guess we have to agree to disagree on this.
> 
> Note that we don't "force" anything here. People can easily configure
> things so that nothing or something else happens when the lid is
> closed. 

I didn't mean one particular option is forced on users, but the change
of the behaviour - us who prefer no suspend on lid close had our choice
changed. I think it is safe to assume most users before getting systemd
in an update have had a tool which have been governing such behaviour
(often included in DEs) if they wanted it, most of the tools don't know
how to override systemd yet, because it's a new thing, so it would be
considerate to the users to assume by default the tools are handling it,
until such time when most of the tools are programmed to control systemd
config.

They are already threads in few days on problems stemming from this
defaults decision just on the forum of the distribution I use:
https://bbs.archlinux.org/viewtopic.php?pid=1167868
https://bbs.archlinux.org/viewtopic.php?id=149711&p=1
https://bbs.archlinux.org/viewtopic.php?pid=1168684

Jiri

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20121003/878cfc2b/attachment.pgp>