After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 779300 - Forceful autosuspend on tablets needs configuration of its own
Forceful autosuspend on tablets needs configuration of its own
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Power
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-02-27 09:24 UTC by Jani Nikula
Modified: 2021-06-09 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jani Nikula 2017-02-27 09:24:22 UTC
This is related to bug 764723 and bug 743456, both of which suggest to file a new bug on the tablet autosuspend on screen blank behaviour.

The claim is that no setting is required for enabling/disabling autosuspend on screebn blank on tablets, because it can be configured by changing the chassis type using hostnamectl.

Autosuspend on tablets is behaviour, while chassis type is a property of the chassis. The chassis type is a reasonable source for the default behaviour. If the user wants to change the behaviour on a tablet, it is unreasonable to require a change (essentially a lie) in chassis type to change that.

The chassis type information is unreliable, and the automatically gathered information may be incorrect, but that is only slightly relevant here. The goal should be that if the information is incorrect, it will be manually set to the correct value using hostnamectl to reflect the actual chassis type.

You are assuming that you are the only consumer of chassis type, and you are assuming that it is okay for other consumers of chassis type to have it be set to an incorrect value to avoid autosuspend. You are conflating behaviour with chassis type.
Comment 1 André Klapper 2021-06-09 16:29:21 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.