Anyone have any tricks for preventing the screensaver from starting on
GNOME? Ideally there would be a simple object :)
.hc
"Making boring techno music is really easy with modern tools, but with
live coding, boring techno is much harder." - Chris McCormick
To answer my own question, it seems to be this command:
gnome-screensaver-command --deactivate
.hc
On Jun 24, 2010, at 10:40 AM, Hans-Christoph Steiner wrote:
Anyone have any tricks for preventing the screensaver from starting
on GNOME? Ideally there would be a simple object :).hc
"Making boring techno music is really easy with modern tools, but
with live coding, boring techno is much harder." - Chris McCormick
There is no way to peace, peace is the way. -A.J. Muste
Indeed. gnome-screensaver-command -d does the trick. You are faster than your own shadow, HC. Because both your emails arrived at the same time to my inbox =P.
On Thu, Jun 24, 2010 at 3:47 PM, Hans-Christoph Steiner hans@at.or.atwrote:
To answer my own question, it seems to be this command:
gnome-screensaver-command --deactivate
.hc
On Jun 24, 2010, at 10:40 AM, Hans-Christoph Steiner wrote:
Anyone have any tricks for preventing the screensaver from starting on GNOME? Ideally there would be a simple object :)
.hc
"Making boring techno music is really easy with modern tools, but with live coding, boring techno is much harder." - Chris McCormick
There is no way to peace, peace is the way. -A.J. Muste
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Thu, 24 Jun 2010, Hans-Christoph Steiner wrote:
To answer my own question, it seems to be this command: gnome-screensaver-command --deactivate
Ah, I would have more readily found :
killall gnome-screensaver rm -f /usr/bin/gnome-screensaver
Because, compared to xscreensaver, gnome-screensaver really follows the mentality outlined in Uncyclopedia :
« If you find a feature, it might confuse a user, so remove it. »
Because none of the options of each screensaver are available in the GNOME dialogues, despite the fact that there's a shitload of XML interface files coming with the plugins, and that the only goal of those files is to actually allow to to build those dialogues automatically, and despite the fact that it's already implemented with Gtk outside of the GNOME distribution, possibly in a programme that gnome-screensaver is a fork of.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On Jun 24, 2010, at 11:15 AM, Mathieu Bouchard wrote:
On Thu, 24 Jun 2010, Hans-Christoph Steiner wrote:
To answer my own question, it seems to be this command: gnome-screensaver-command --deactivate
Ah, I would have more readily found :
killall gnome-screensaver rm -f /usr/bin/gnome-screensaver
Because, compared to xscreensaver, gnome-screensaver really follows
the mentality outlined in Uncyclopedia :« If you find a feature, it might confuse a user, so remove it. »
Because none of the options of each screensaver are available in the
GNOME dialogues, despite the fact that there's a shitload of XML
interface files coming with the plugins, and that the only goal of
those files is to actually allow to to build those dialogues
automatically, and despite the fact that it's already implemented
with Gtk outside of the GNOME distribution, possibly in a programme
that gnome-screensaver is a fork of._ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
After all that, I ended up having to add some stuff to /etc/X11/ xorg.conf because of fglrx/ATI issues:
Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection
It would be awesome to have a [screensaver] object that worked on all
platforms, so you could just hook up a toggle to it and control the
screensaver... I whipped up some rough, simple versions:
.hc
If you are not part of the solution, you are part of the problem.
On Thu, 1 Jul 2010, Hans-Christoph Steiner wrote:
After all that, I ended up having to add some stuff to /etc/X11/xorg.conf because of fglrx/ATI issues: Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection It would be awesome to have a [screensaver] object that worked on all platforms, so you could just hook up a toggle to it and control the screensaver... I whipped up some rough, simple versions:
Is that all you have to do nowadays ?
I think that back in 2003 or so, I had to hunt down four settings in four different places, one as a "xset s off" command, one as "killall xscreensaver" (or the equivalent in a dialogue), one as... perhaps another "xset" command about dpmi, and then there was a BIOS setting.
I overlooked one of the four settings, and it was a big shame, as a gallery employee had to come in several times per hour to press any key.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On Jul 1, 2010, at 2:53 AM, Mathieu Bouchard wrote:
On Thu, 1 Jul 2010, Hans-Christoph Steiner wrote:
After all that, I ended up having to add some stuff to /etc/X11/ xorg.conf because of fglrx/ATI issues: Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection It would be awesome to have a [screensaver] object that worked on
all platforms, so you could just hook up a toggle to it and control
the screensaver... I whipped up some rough, simple versions:Is that all you have to do nowadays ?
I think that back in 2003 or so, I had to hunt down four settings in
four different places, one as a "xset s off" command, one as
"killall xscreensaver" (or the equivalent in a dialogue), one as...
perhaps another "xset" command about dpmi, and then there was a BIOS
setting.I overlooked one of the four settings, and it was a big shame, as a
gallery employee had to come in several times per hour to press any
key.
Well, I did do other things, but it was the final thing that actually
seemed to work. Perhaps I needed to do all of them. I also did:
xset s off apt-get remove gnome-screensaver (set the screensaver and power management prefs to none)
That's why it would be awesome to have this all in a simple-to-use
[screensaver] object. I added some more stuff to my [gnome-
screensaver] object:
.hc
Programs should be written for people to read, and only incidentally
for machines to execute.
- from Structure and Interpretation of Computer Programs
On Thu, Jul 1, 2010 at 12:45 AM, Hans-Christoph Steiner hans@at.or.at wrote:
Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection
Haha, that's so funny, I had to deal with the same problem just 2 days ago (and I note, you too)! I did not get any xorg.conf setting working for some reason (nVidia GPU) but finally what I managed to accomplish was turn off gnome power-management (in fact, I unchecked all gnome services from the Startup Applications, I did not need any of them) and I added a simple script to the Startup Application that run the necessary stuff. in that script I included the following: xset s off xset s noblank #not sure if actually needed but xset -q shows that I prefer blanking even after I set it to off xset -dpms xset dpms 0 0 0 # this I think is equivalent to your ServerFlags and maybe redundant after the above
Only then I was able to prevent the screen from dimming. I did not remove gnome-screensaver, however.
./MiS
-
Hans-Christoph Steiner -
Hans-Christoph Steiner -
Mathieu Bouchard -
Michal Seta -
Pedro Lopes