On 05/04/2011 12:05 AM, Jesse Hutton wrote:
On Tue, May 3, 2011 at 2:16 PM, Olav Vitters <olav vitters nl>
wrote:
On Tue, May 03, 2011 at 10:59:58AM -0700,
Sriram Ramkrishna wrote:
> For me suspend works.. I can successfully suspend..
It's coming out of
> suspend that cause a problem. In which case, even
though suspend work,
> re-animation is broken. So it needs to detect both
parts. For me I think
> it's some kind of problem with my disk (SSD) and not
the usual graphics
> driver.
I meant that: Only say suspend works if the whole thing works.
E.g. When going to suspend, set some flag somewhere and sync
it to disk.
When coming out of suspend, remove the flag. Now when booting,
check if
the flag is set. If so, ask to/disable suspend.
Then the whole UI will automatically adjust because it will
know suspend
is broken.
--
Regards,
Olav
That still wouldn't work for some cases, including mine: my
desktop resumes, but the fan noise is intolerable until I
reboot.
Why is Gnome Shell relying so heavily on something that is
notoriously difficult to make work across a wide array of
hardware configurations?
And why discourage shutting down to begin with? It saves
power and booting is getting faster all the time anyway...
Jesse
I believe that in Vista as well, the "shutdown" button was relegated
to a less accessible position in favour of Suspend. I agree that it
makes more sense for laptop users than desktops, but suspend being
the next best thing to the fabled "fast-boot", it (suspend) does
need to be fixed; but not by Gnome.
|