Red Hat Bugzilla – Bug 546497
maybe we shouldn't suspend on lid close if using external inputs and outputs
Last modified: 2015-01-14 18:24:21 EST
Today we suspend on lid close. Perhaps we should support the following cases:
a. Shut lid while docked with external monitor, keyboard, mouse
For this I think we should not suspend while it is still possible to interact with the system. In the even all of the external outputs are removed (LCD disconnected) I think we should probably suspend. We probably can't do something similar for inputs because there can be may different types of inputs - even the outside of the laptop case can have input controls on it.
b. Shut lid while watching movie on attached TV
For this I imagine that we'd not suspend until the system goes idle after the movie ends.
c. Shut lid when it is the only output
I work with my laptop in a dock, so it is often connected to an external display. As soon as I close the laptop lid, power manager will blank the screen, despite the fact I have an external display connected.
Yes, this should be fixed, it's very annoying behaviour.
The most simple fix is to add "Do nothing" option for "When laptop lid is closed" in gnome-power-manager. Better fix is described in the original post on this bugzilla entry.
I use my laptop very often in a docking station, so I only have the external DVI display in use.. So I don't want to blank the (external) screen when laptop lid is closed!
Btw there's a workaround described here:
It seems we have another bugzilla entry about this issue:
(and also: https://bugzilla.redhat.com/show_bug.cgi?id=598540).
*** Bug 598540 has been marked as a duplicate of this bug. ***
Upstream has re-added "Do nothing" as an option:
Another option is definitely not the answer.
Is anyone working on fixing these multi-display bugs?
There's another bugzilla about the same bug/problem here:
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.