desktop-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Retitling and reopening as per previous comment.

However, I still don't understand the rationale for having a machine
type whitelist.; see (2) in comment 5. Do we have hard data that
hibernation is consistently broken on some particular hardware, and the
reason isn't just partitioning?

My gut feeling is that we should just disable hibernation by default,
period (and perhaps provide an Ui configuration bit to enable it).
Maintaining and checking a whitelist will just cause a lot of
unnecessary effort which won't actually help a lot.

** Summary changed:

- Disable suspend/hibernate options when they are not supported
+ Disable hibernate option when it is not supported

** Changed in: gnome-control-center (Ubuntu)
       Status: Won't Fix => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/812394

Title:
  Disable hibernate option when it is not supported

Status in Ayatana Design:
  New
Status in “gnome-control-center” package in Ubuntu:
  Incomplete

Bug description:
  Id like to proposse a change in the design of Power preferences in the
  GNOME control center: https://wiki.ubuntu.com/Power

  Instead going throuh the "certification" path, we can simply disable
  the options about suspend/hibernate if Its not supported in the
  current hardware (we have api for this in upower)

  I think this solution is more scalable, as we do not need to maintain
  a database with "certified" hardware. Also, we can add a button or a
  informative text when suspend/hibernate doesnt work to guide the users
  about what to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/812394/+subscriptions