Hi Thanks for the additional information. Yes tigervnc is probably the best option. It is on my todo list, but it has been there for at least three years now so I guess it will not happen (by me) anytime soon. :-(
// Ola On Wed, Aug 19, 2015 at 11:40 AM, Sascha Silbe < [email protected]> wrote: > Dear Ola, > > Ola Lundqvist <[email protected]> writes: > > > I'll see what I can do. The package is up for adoption as I have little > > spare time (kids...), but I'll see if I can get some free time some day. > > TL;DR: TightVNC 2.x is Windows-only. Cannot send Option key with any > non-Apple VNC viewer to the built-in Mac OS X VNC server. > > When trying to install TightVNC 2.7.10 locally for the time being, we > noticed that there actually is no TightVNC for Unix anymore, despite > what the home page says. There is TightVNC 2.7.10 for Windows and there > is the TightVNC Java Viewer 2.7.2. That's it. :-/ > > We got TigerVNC installed locally, but couldn't get the Option key to > work at all using any of the key symbols that were mentioned anywhere > related to VNC on Mac OS X or that might have made sense in this context > (Meta_L/R, Alt_L/R, Hyper_L/R, ISO_Level3_Shift, Mode_switch, > Menu). Even if we send the same sequence ("xte 'keydown Shift_L' > 'keydown Meta_L' 'sleep 1' 'keyup Shift_L' 'keyup Alt_L'") the built-in > Mac OS X VNC client sends when connected to vnc4server running on Linux, > it doesn't work. So AFAICT there's no way for a non-Apple VNC viewer > that will make the built-in VNC server of Mac OS X trigger an Option key > press (it does work using the built-in Apple VNC viewer). Anyone who got > the Option key to work probably is using a third-party VNC server on the > Mac OS X side. > > We've given up on controlling the Mac via VNC for now as there were > other issues as well (dragging something in Xcode didn't work and there > were no apparent other ways of achieving the same result). Might try > again using a third party VNC server some other time. > > So while having TigerVNC (not TightVNC as there is no Unix version > anymore) in Debian would be great, it doesn't really solve the Option > key issue. The fix in TightVNC 2.7.10 is probably for the Windows > TightVNC viewer to properly send the "Windows" key (Super_L). The VNC > viewers available in Debian already send the key presses as-is, it's the > server side that doesn't handle them correctly. > > Sascha > -- --- Inguza Technology AB --- MSc in Information Technology ---- / [email protected] Annebergsslingan 37 \ | [email protected] 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
