You are not logged in.
In the bug I posted at Gnome, someone pointed out that this problem only seems to occur when the display sleep value is set at "Never" in gnome-power-manager. I switched my setting to the next highest value, 2 hours and 1 minute, and am finding this to be the case as well.
Nice solution!!! i've been pulling out my hsir of my head for the last few days with this bug because it suck to be moving the mouse all the time when trying to read something. The display was blanking here in about 20 secs!!!
Now it seems to be fine! hope the update comes soon.
thanks to you and gnome-dev-teamfor the simple (and tricky) solution.
Arch Linux X86_64 (Pure 64bits Blend)
Kernel 2.6.29.3 w/ KMS and ext4fs -
Xorg 1.6.1 w/UXA - Gnome 2.26.1 - compiz 0.8.2
Offline
There are a couple other solutions that work as well, described above in this thread. My "xset -dpms" solution (which means the screen really will never power off) and eldragon's deleting the .gconf folder solution (warning, you'll lose all your system preferences, I think), which I haven't tried yet.
Offline
There are a couple other solutions that work as well, described above in this thread. My "xset -dpms" solution (which means the screen really will never power off) and eldragon's deleting the .gconf folder solution (warning, you'll lose all your system preferences, I think), which I haven't tried yet.
yes you will definately lose all settings on your gnome desktop. i actually moved it first to a backup in order to debug my other issue with ooffice, but when i moved it back (to do a more fine grained settings) it didnt stick beats me (this is a warning on moving it to test this too and trying to revert your actions) someone more knowledgable could explain what happened to me
Offline
In the bug I posted at Gnome, someone pointed out that this problem only seems to occur when the display sleep value is set at "Never" in gnome-power-manager. I switched my setting to the next highest value, 2 hours and 1 minute, and am finding this to be the case as well.
That didn't fix it for me. Even with 2h 1m my monitor is still going to sleep after ~1m.
Offline
ive changed the "put display to sleep when inactive for" to 2hs and it started happening again, when put to something lower (1.38hs) it disappeared....
there is a similar bug in inkscape where you cannot slide stroke properties to the upper most value (0xFF), its apparently related to the gnome API being strengthened in preparation to gtk3 (something like this ive read). maybe these issues are related...
Offline
That didn't fix it for me. Even with 2h 1m my monitor is still going to sleep after ~1m.
Hmm, it's still working for me. Did you try the other solutions suggested in this thread? I suggest my "xset -dpms" solution (see above), which also works fine for me.
Offline
Of course the xset -dpms works (as well as setting off time in xorg.conf, I've already done that), but it's hardly a 'solution' (and neither is changing the sleep time, it's a bit less hackish though).
Offline
You know, I'm new to all this stuff and I was just trying to be helpful. It seemed from your post like you had not found a way to get your monitor to stop turning off all the time. As the person who started this thread, I'm just reporting to people what I know or have figured out. I'm sorry I don't have an idea that you like better. I'm not a developer and I'm not a programmer.
Offline
Oh, sorry if I offended you. English is not my native language and I may have problems with some linguistic nuances. From my point of view my post was purely informational. ;)
Offline
Okay, thanks. Good luck finding a solution for the backlight going off that works for you. I guess I've decided that the xset -dpms or settig the time to 2 hours is a good enough work around for me. Hopefully this will get fixed in a future version of gnome-power-manager, although so far my bug report at Gnome doesn't seem to be getting any attention.
Offline
We just have to wait. The problem with these, er, monoliths, like Gnome or Wine is that the bug reports take a while to process. Especially if it's something as insignificant as this.
Offline
I set the sleep and display sliders to 2 hours and 1 minute in the power manager dialog, but when I booted again today they were all the way down at the minimum of 11 minutes. For now, I've settled on using xset -dpms until something better comes along.
Running Arch on Eee PC 901 12 GB
Offline
for my desktop with gconf-editor in apps > gnome-power-manager > general i uncheck "can_hibernate" and "can_suspend" and it works!!
I dont know if this works for laptops
Offline
I've noticed lately that with the sliders set to 2 hours and 1 minute it actually doesn't entirely solve the problem for me. The backlight doesn't go off after thirty seconds all the time, like it did before, but after five or ten minutes it will. I may go back to the xset -dpms way.
Offline
Same problem here... Only found "xset -dpms" to fix it... quite annoying !
Offline
Just a note that installing gnome-power-manager-notify-osd 2.24.4-5 from AUR with yaourt (removing gnome-power-manager-2.26.1-2 first, of course) fixed both the LCD blanking problem and the issue with my UPS not showing up. The package is marked out of date but there are other distribtions running gnome-power-manager-2.24 on gnome 2.26 with good results. It works fine here.
Don't break the silence unless you can improve upon it.
Offline
Yeah.. I'm going back to gnome-power-manager 2.24 myself
Offline
2.27.something was released. maybe you can give it a try.
Give what you have. To someone, it may be better than you dare to think.
Offline
Let it hit the repos..
Offline
I'd like to add that I have this issue only with my Arch32 on a P4 with an old analogue monitor. On my C2D rig with Arch64 and LCD monitor connected via DVI everything's fine.
Last edited by Aidenn (2009-06-04 15:32:50)
Offline
Let it hit the repos..
in September )
Give what you have. To someone, it may be better than you dare to think.
Offline
2.27 is just a development step stone to the stable 2.28. Only the stable versions of Gnome tend to come up in the repos.
Offline
I'd like to add that I have this issue only with my Arch32 on a P4 with an old analogue monitor. On my C2D rig with Arch64 and LCD monitor connected via DVI everything's fine.
For what it's worth, I have the problem with Arch64 on my laptop, with Core 2 Duo.
Offline