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 681938 - Drive Spin down - polkit nag
Drive Spin down - polkit nag
Status: RESOLVED OBSOLETE
Product: gnome-power-manager
Classification: Deprecated
Component: general
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-08-15 19:30 UTC by Dominique Leuenberger
Modified: 2020-11-06 20:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dominique Leuenberger 2012-08-15 19:30:54 UTC
Issue was originally reported downstream:
https://bugzilla.novell.com/show_bug.cgi?id=548858

>my energy setting in gnome should spin down disks when i have only battery...
>
>the problem is that i must type root password for that any time. and it's quite
>annoyning
>

Now, of course, this is an issue of how the polkit default privileges are defined (and has since been adjusted in openSUSE).

Yet, there is an issue with this approach, as the user can potentially set a spin down every 1 second of idle, allowing to be rather rude on the disks (no issue with SSD of course).

An admin should have several additional 'options'
- Do not grant the user to spin down (default polkit setting); but do not nag the user about it
- Possibly have a 'saner' value restriction, where the admin can give 'lower boundaries'
Comment 1 André Klapper 2020-11-06 20:14:17 UTC
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.