Hi Rodolfo, debian developers,
* Gregor Zattler telegr...@gmx.net [2013-07-27; 10:47]:
* Gregor Zattler telegr...@gmx.net [12. Jul. 2013]:
* Rodolfo García Peñas k...@kix.es [12. Jul. 2013]:
Probably the bug could be here:
module new.c:
173 /* Work around stupid X11 bug: When switching
Hi Rodolfo,
* Gregor Zattler telegr...@gmx.net [12. Jul. 2013]:
* Rodolfo García Peñas k...@kix.es [12. Jul. 2013]:
Probably the bug could be here:
module new.c:
173 /* Work around stupid X11 bug: When switching immediately after the
command
174* is entered, the enter button may
Hi,
I am not sure, but...
Probably the bug could be here:
module new.c:
173 /* Work around stupid X11 bug: When switching immediately after the
command
174* is entered, the enter button may get stuck. */
175 if (getenv(DISPLAY) != NULL)
176 sleep(1);
Probably the problem is not
Hi Rodolfo,
* Rodolfo García Peñas k...@kix.es [12. Jul. 2013]:
I am not sure, but...
Probably the bug could be here:
module new.c:
173 /* Work around stupid X11 bug: When switching immediately after the
command
174* is entered, the enter button may get stuck. */
175 if
Hi Rodolfo,
* Rodolfo García Peñas (kix) k...@kix.es [19. Jun. 2013]:
I cannot reproduce the problem :-(
But, I cannot understand the behaviour.
1. xautolock calls vlock. xautolock waits vlock to unlock the screen.
2. vlock (shell script) calls vlock-main
When vlock-main finish (the
Hi,
I cannot reproduce the problem :-(
But, I cannot understand the behaviour.
1. xautolock calls vlock. xautolock waits vlock to unlock the screen.
2. vlock (shell script) calls vlock-main
When vlock-main finish (the user enter the right passwd), then, and
only then, xautolock should unlock
6 matches
Mail list logo
