Re: Triggering gnome screen-saver timeout from console keypresses?

[Mario Lang <mlang delysid org>]

Samuel Thibault <samuel thibault ens-lyon org> writes:

> Unfortunately there is no way for the X server to know that things are
> being typed in the console, since it's the kernel that handles that.

It is true that the kernel handles that, but it isn't quite true that
there is "no way" for the X server to still monitor keypresses.
One technically doable solution would be for the X server
to listen in on the linux input event interface.  That might still
mean some portability issues, but my main concern is actually Linux, which
is what I am using, so it should indeed be doable somehow.

> The X server knows when it loses focus however.

Well, thats of no use here since if the X server looses focus
but no further keyboard interaction happens, the screen saver
should still start to protect the users account...

> Mario Lang, le Wed 13 Aug 2008 18:47:25 +0200, a écrit :
>> However, since the braille support for gnome-terminal is still lacking
>> a few things
>
> Do you know that you can run a second brltty to handle reading them?
> Something like
> brltty -b ba -x as 

I know of it, but it doesnt really work for me.
I dont know if I do anything wrong, but if I invoke
the command above, I only see the prompt on my display and
moving up/down does immediately give me the "end of screen" beep,
as if there was just one line in the terminal.  After a bit
of fiddling back and forth, brltty seems to die again and I
see the Orca representation of that terminal...
Maybe you can tell me what I need to do to get this working?

>> The X11 screen saver has kicked in every time I switch back to my X11
>> console (Alt+F7).
>
> It's not only that, but animated screen savers may also eat CPU...

Well, that might be true, but is also easy to fix by configuring
an appropriate screen saver setting I guess?

> These screen savers have always been a problem, e.g. while playing a
> movie in a webbrowser, etc. :/

>>  1.) A hack that I could use to fix this ASAP?
>
> Disable the screen saver :)

I am afraid my company security policy does not allow for that.
Besides, I think the timeout feature is a useful one, it just needs
to work properly :-).

>>  2.) A way to fix this permanently for everyone else (i.e., something we could
>>      implement upstream so that console keypresses are taken into account
>>      by default)?
>
> As I said, it doesn't fit the current scheme.  The only relatively easy
> thing to do would be to get screen savers disabled when switching off
> from the X server.  Some people may not be happy with that either,
> however.  I guess we should forward the issue to xorg freedesktop org .

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
  .''`. | Get my public key via finger mlang/key db debian org
 : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
 `. `'
   `-      <URL:http://delysid.org/>  <URL:http://www.staff.tugraz.at/mlang/>