← Back to team overview

desktop-packages team mailing list archive

Re: [Bug 812394] Re: Disable suspend/hibernate options when they are not supported

 

On Thu, 2011-08-18 at 15:55 +0000, Martin Pitt wrote:
> Ted Gould [2011-08-18 14:13 -0000]:
> > So do you feel we can assume that on all machines suspend works?
> 
> It certainly doesn't, but at least it "works" on far more machines
> than where it doesn't. Reportedly suspend sometimes fails randomly,
> when you have particular peripherals attached, or suspend too many
> times, etc.), but that wouldn't be helped with a by-machine whitelist
> either.

I guess the point here Martin is that you're saying "we don't know" --
and that leads to very confused designs that say we don't know to the
user, and thus the user doesn't know.  Then they have no confidence in
us to tell them anything!

I think that we need to come up with a "yes" or "no" answer to the
question: "Does suspend work?"  Or "yes, with a blacklist" or "No, with
a whitelist" would also work.

Do you think this would be a good thing to put on the technical board's
agenda?

-- 
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 suspend/hibernate options when they are not supported

Status in Ayatana Design:
  New
Status in “gnome-control-center” package in Ubuntu:
  Won't Fix

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


Follow ups

References