GNOME Bugzilla – Bug 617999
maybe we shouldn't suspend on lid close if using external inputs and outputs
Last modified: 2020-11-06 20:14:14 UTC
Filed downstream as https://bugzilla.redhat.com/show_bug.cgi?id=546497 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 Suspend immediately.
I'm not sure even the kernel knows if we are docked right now (ACPI sucks etc) -- could we use some kind of metric to guess this kind of data? I agree that suspending on lid close is sometimes not what you want to do.
I am not sure that the technical docking is that important but rather the fact that system is still able to be controlled and viewed from an external keyboard and monitor.
c. is the one that makes it problematic for people moving from the office to a meeting room and close the lid after undocking the laptop. Is the rationale here that we should stop papering over bugs wrt suspend by adding options to cater for all the broken cases or is it something else that triggered the decision to make suspend the default on lid close?
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.