Hi Michael. I have experienced this too. The screensaver gets locked and just doesn't come back to give you an unlock prompt. I worked around it by logging in remotely to the system running the VNC server, and then killing the xscreensaver that was running. The more permanent solution would probably be to disable the screensaver in the first place after logging into the VNC session. If you already need a password to get into the session, I don't see a point in having an additional screen locking mechanism.
-- Alan michael schuster wrote: > All, > > I hope these are the right places for this question - if not, please > redirect and keep me on CC. thx. > > I've been sucessfully accessing a vnc session running on my > workstation in Menlo Park for the last few weeks. Today I tried to > access this session, only to find that I couldn't unlock this session > if it had been inactive for a few hours. > > here's what I did: > while in the Bay Area > - logged out of my X session on my workstation (just in case anybody > wanted to use it ;-) > - ssh'd into my WS and ran 'vncserver ....' > - ran 'vncviewer ...' > all without issue. Unlocking a session that had been idle overnight or > over the weekend: no problem. > > this morning, in Europe, I > - punched in (to .sfbay) > - tried the same 'vncviewer ...' command. All I got was a black screen > (ie the dialog prompting for my password didn't come up) > - after some time (5 minutes?), I ssh'd into my WS, 'vncserver > -kill'ed the vnc session, started a new one. > - 'vncviewer ...' worked fine (if noticably slower, what a surprise ;-) > - locking and immediately unlocking worked fine. > - punched out (including killing vncviewer), closed down laptop, left > for extended lunch break > - punched back in, vncviewer again shows me only blank screen. I > waited a little, no change. I even tried remote display of a vncviewer > running on my WS (it was sluggish), but I didn't get to unlock the > session. > > TIA for any ideas. > Michael
