Re: gnome-list Digest, Vol 90, Issue 1 Item 1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 03/10/11 13:00, gnome-list-request@xxxxxxxxx wrote:
Send gnome-list mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gnome-list digest..."

Today's Topics:

    1. Gnome 3.2 - How can I completely disable Suspend? (Adam Sailer)


Message: 1
Date: Sun, 2 Oct 2011 18:53:07 -0700
From: "Adam Sailer"<ASailer@xxxxxxx>
Subject: Gnome 3.2 - How can I completely disable Suspend?
Content-Type: text/plain;	charset="us-ascii"

I've downloaded and installed from the openSUSE-based Gnome 3.2 live disk.

Laptop model is Dell XPS M1330
Video is NVidia GeForce 8400M GS
Kernel ver is x86_64

1 - Nouveau driver TANKS when system goes to suspend. Comes back with black
screen and mouse pointer. Must ctrl-alt-backspace to reset X-server.
2 - NVidia driver repository driver ver 275.21 TANKS when system goes to
suspend. Desktop comes back, but is completely frozen except for the mouse
pointer. Must ctrl-alt-backspace to reset X-server.
3 - NVidia's latest driver ver 280.13 causes random lock-ups. Completely


Also noticed that the wireless network adapter is unusable after attempting
to resume from suspend, and the system's fan spins up during suspend

I've experimented by uninstalling pm-utils; this has resulted in Gnome 3.2
menu replacing "Suspend" with "Power Off"; this also changes screen settings
from "Suspend  after" to "Turn off after". Once this time-limit is reached,
Gnome becomes unresponsive and ctrl-alt-backspace is required.

Why does this menu not have a "NEVER" option? This might be fine-and-dandy on
a tablet, but these issues prevent me from using Gnome 3+ on any machines
that I do work on...

The suspend function is somewhat hardware dependent. Indeed the whole ACPI process is hardware dependent.
Many machines use ACPI perfectly but some most certainly do not.

Amongst the computers which do not work correctly with ACPI are some Samsung models.
In my Experience ASUS are amongst the ones which work the most correctly.
(You have not mentioned the make and model of the computer (or motherboard) or which Distro you are using)

When I install a Laptop, one of the final checks is shut the lid and after some seconds open it again. It should come up with page asking for user password and after some seconds the Wi-Fi connection re-establishes. I do not waste time trying to solve the problem if it does not work correctly as, again in my experience, with each update of kernel the situation improves.

As example one particular Samsung would not power down and had to forced (by holding power button for more that 5 seconds) and then a new release, and now it worked correctly on the power down but it still does not resume correctly, maybe next year? (using Mandriva, my favourite Distro)

As regards the 'NEVER' look at your 'Preferences-Screensaver' and 'Preferences-PowerManagement'
gnome-list mailing list

[Home]     [Fedora Desktop]     [Kernel List]     [Red Hat Install]     [KDE]     [Red Hat Watch List]     [Red Hat Development]     [Red Hat 9 Bible]     [Red Hat 9 Mailing List]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

Add to Google Powered by Linux