On Tue, 2010-01-19 at 13:23 +0100, Bruno Kleinert wrote: > Am Freitag, den 15.01.2010, 17:32 +0100 schrieb Bruno Kleinert: > > Maybe there's something in the logs on my amd64/Radeon system. I'll look > > at these files tomorrow. > I had some annoying trouble to suspend the machine. To make things > short: For the whole weekend I only got two cycles of suspend -> resume, > as the box locks up when the system is snapshotted... > > But I found out something interesting: I'm using GNOME as desktop > environment, so I'm also using gnome-screensaver. Quite funny: If I make > GNOME *not* start the gnome-screensaver, then, of course, the screen > doesn't get locked by the gnome-screensaver when the machine is > suspended and resumed. But then I get *no* black screen after the > resume, and also switching to a text console shows up text! > > Maybe it's some crazy bullshit, but I have a guess where this could come > from: ;) gnome-screensaver fades the display to black when it gets > active, maybe this is done by manipulating color/contrast/whatever > settings (?). I guess so, because the text "snapshotting the system" at > the text console is often very dark and sometimes invisiable after > gnome-screensaver got active to lock the screen before the machine > starts the suspend procedure. > Now, if the machine gets resumed, maybe these color/contrast/whatever > settings don't get successfully restored or restored at all.
If that is the case, running something like DISPLAY=:0 xgamma -gamma 1.0 from an ssh login might restore the display. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org