Created attachment 54625 [details]
Peter Estrand's fix

Fixed in 3.3.3r2-29.

Two questions:

Is bug 40650 a dup of this one?

Is bug 66890 (xscreensaver fails to grab keyboard when VNC is running
fullscreen) caused by this patch?

*** Bug 40650 has been marked as a duplicate of this bug. ***

According to bug 66890, this patch was removed... 

Is there some way of fixing this w/o causing bug 66890? May be fix the WMs that
cause it?

As Peter Estrand says in the link at bug #66890, basically we don't know. 
 
The main fullscreen problem that this bug was originally about when I opened 
it was that fullscreen plain didn't work at all---all keyboard events get 
lost.  That _should_ still be fixed in 3.3.3r2-34. 
 
There is another minor issue to do with when the resolutions are different and 
the placement of the cursor, which is easily worked around (put the cursor in 
the right place!). 
 
Changing state to modified until fullscreen is verified to actually work in 
3.3.3r2-34.

I've installed 3.3.3r2-34 on Red Hat 7.2 + all updates (e.g. kdebase-2.2.2-1 and
xscreensaver-3.33-4). Now -fullscreen works properly  and xscreensaver locks
properly when VNC is running fullscreen. Thanks so much for fixing this!

Haven't yet tried using it on a newer system though...

Even with vnc-3.3.3r2-34 there is still one fullscreen-related problem left
(should I report it in a separate bug?). If the VNC screen size is bigger than
the local screen size,then in fullscreen mode I can not scroll down (e.g. by 
trying to go past the lower end of the screen) until I switch to windowed mode
and then back to fullscreen. And even if I start in windowed mode, I still have
to go thorough switching 3 times ( -> fullscreen -> windowed -> fullscreen)
before I am able to scroll down. Scrolling down in the windowed mode and
scrolling right in both modes works OK. All of this is still on 7.2+updates.

Does this still happen with vnc-3.3.3r2-43?

Can't reproduce this in vnc-3.3.3r2-43; starting viewer with -fullscreen works.