At Fri, 28 Feb 2014 08:38:49 +0100, Stefan Seyfried wrote:
Am 26.02.2014 01:25, schrieb Jan Engelhardt:
On Wednesday 2014-02-26 00:06, Greg Freemyer wrote:
That's a very wrong assumption. An obvious counter case is to use a laptop as a server.
It may be a counter case, but not a very _common_ case.
Possibly not common, but I've done it. And the whole concept of using a raspberry pi as a server is similar.
There is yet a RPI to show up with a lid, though.
But there's lots of X86 hardware with broken Firmware.
I have a desktop here which shows a (reportedly connected!) LVDS display, even though the only connector is a VGA cable, leading GDM to output the login window on the LVDS display. And the users wondering why the screen does stay black after boot.
I'd almost bet that you can find desktop motherboards which pretend to have a lid switch (and which is of course always closed).
Right. Of course, they are minority. But there are. And, speaking of minority, we can't forget about Braille output. Would logind detect it dynamically? Yet another example: you boot (lid closed) with the connection to a TV while TV is powered off. Then no external monitor is detected, so the machine goes to suspend, because logind thinks you turned on the machine accidentally. There must be some reasons why such an action (checking the lid state at start up and going to suspend immediately) wasn't implemented in the desktop environment. It's different from closing the lid while running.
And if there is a lid, you can change the behavior, as Claudio mentions. It's just a default.
Well, that's different from what Raymound wrote.
We'll see. A sensible openSUSE default would then be to disable all suspend by systemd and let the desktop environments handle it.
I sincerely hope so... Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org