Bug 332410 - gnome suspend causes dark screen
Summary: gnome suspend causes dark screen
Status: RESOLVED INVALID
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: i386 openSUSE 10.3
: P5 - None : Major with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-10 01:37 UTC by Anthony Tuel
Modified: 2007-11-13 13:26 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony Tuel 2007-10-10 01:37:36 UTC
Running SuSE 10.3 on a Lenovo Thinkpad z61p after upgrading from SuSE 10.2 and alls working well except suspend. I am running the ATI driver that worked properly under SuSE 10.2.  

When I press Fn+F4 to suspend, the screen goes very dark/brownish shades of everything and then properly suspends.  On resume, it comes back up properly but the very dark brownish shades exsist over everything.  I can still work with the windows, etc just as normal but everything is very dark/brown.

So first, had to add the s3bios to kernel parameters in grub and to the /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenvo.fdi file.  I also had to put z61p in for the hardware version as well:

---snip----
     <!-- T60*, Z61* -->
      <match key="system.hardware.version" prefix="ThinkPad ">
        <match key="system.hardware.version" suffix="T60">
          <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
          <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
        </match>
        <match key="system.hardware.version" contains_outof="T60p;Z61m;Z61p;Z61t;Z60m">
          <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
          <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
        </match>
      </match>
---snip---

So doing that got the suspend to work properly, etc when executing pm-suspend.  There is no darkening of the screen on resume, etc.  

Digging through the logs, I realized it was the gnome-power-manager which was executing the suspend.  I executed this from the command line and got these results:

:~> gnome-power-cmd.sh suspend
Suspending
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

and right away after executing the command the screen went brown/dark and remained that way after the suspend/resume cycle.

If I log out and back in without restarting X, the colors come back to normal.  I even tried to take a screenshot to show you what the dark/brown looks like, but the screenshot turned out normal colors.

This problem also seems to happen if I let my system sit idle for a while.  I suspect this is just the 15 minute timer I have set.  I have set this timeout to  never now so it should go away, but it'd still be nice to get my Fn-F4 shortcut back working again.
Comment 1 JP Rosevear 2007-10-15 15:08:00 UTC
gnome-power-manager just calls out via dbus (gnome-power-cmd.sh is in fact all dbus commands).  Are you sure the screen is just not dimming brightness wise?
Comment 2 Anthony Tuel 2007-10-15 17:32:53 UTC
The screen is not just dimming... the colors are all way off to the point they cannot even be read.  I also saw this from gnome-screensaver and its calls to dim or turn off the screen after periods of inactivity.  I've removed gnome-screensaver and gnome-powermanager and fallen back on xscreensaver directly and using pm-suspend via hacking the thinkpad acpi script to make that call and now everything is fine.

I'm out of town at the moment and I dont really want to reinstal the gnome-screensaver and gnome-power manager on my primary laptop agprivoxyain now that I have it working in the hacked config, but I have a Thinkpad T60 back at home that suffers the exact same problem.  Once I get back home, since the screen shot doe not capture the color corruption, I'll break out a camera and upload a picture of it.
Comment 3 Stephan Kulow 2007-11-10 17:09:44 UTC
info is provided, picture pending. 
Comment 4 Anthony Tuel 2007-11-13 04:12:03 UTC
I can no longer this this to occur on on my secondary T60.  
Comment 5 JP Rosevear 2007-11-13 13:26:12 UTC
Thanks Anthony.  Please re-open if you can reproduce at some point in the future.