Le Sun, 05 Sep 2010 22:18:33 -0430,
Jose Luis Rivas <ghost...@debian.org> a écrit :
Hello,
> Please, tell us how to reproduce it.
- Swhich to VT or remote ssh acces to the machine
- find hack's pid
schedule a kill on the child eg. sleep 30 ; kill $pid ; switch back to
X-console before the end of slrep command or kill it remotely *should*
reproduce it.
I was probably wrong : killing the process did not resolve screen
locking but was not the reason why it occured.
> How a xscreensaver child dies in
> your machine?
Some hacks dies badly or acts nastily. If I find some I will fill a bug
if necessary.
I did test while upgrading xscreensaver (today) which is most probably a
bad idea. This was weird but I did not lose my X-session that time.
> Which hack were you running?
Worm (/usr/bin/worm (!?) or is that that' this hack has been removed
from xscreensaver ?) and some others . I set up xscreensaver so that it
launches a random hack. And what occured when nasty hack was launched is
that screensaver warns that the hack died unexpectly and then the screen
became totally unresponsive.
Now, worm hack is launched corectly, but as this is a text game, it
is not very beautiful/interesting hack
> Can this be related to your video card?
Yes it is most probably related to nvidia card and "nouveau" driver.
Sorry for noise, it looks like there is no more problems for now (but
I'm now running nvidia proprietary driver).
--
L'expérience est le nom que chacun donne à ses erreurs.
-+- Oscar Wilde -+-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
