How to prevent question mark cursor issue cause be Insert key when doing VNC to a mac?

6

5

I found out that when I press the Insert key on the client I will block the OS X VNC server by putting it in a "help mode" where you get the question mark mouse cursor.

The mouse works but I cannot use the keyboard anymore.

Details:

  • Reconnecting using VNC does not help
  • Normal keyboard is working fine on the mac

The only solution in addition to relogin was to stop the VNC server on mac using:

  killall OSXvnc-server

After few seconds it will restart by itself and it will work.

I don't like current workaround and looking for something better.

Tested with these versions of the VNC client and all put the VNC server in the question mark mode, requiring service restart:

  • Ultr@VNC 1.0.8.2
  • RealVNC 4.1.3

I know that the problem is caused by the different/bad implementation of the VNC protocol in the server but do you need an workaround?

sorin

Posted 2010-01-11T12:35:32.490

Reputation: 9 439

Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) http://discussions.apple.com/thread.jspa?threadID=2222053&tstart=0

– sorin – 2010-01-13T14:59:57.743

Answers

5

From Mac OS X - VNC curson becomes QUESTION mark - unable to type (with experts-exchange.com you might need to google for it, then scroll to the end to see the answers):

Answer 1:
This problem occurs when you use UltraVNC version 1.0.5.2 (possibly anything 1.0.5.+?) and hit the INSERT key on a Windows machine. At that point your only option appears to be to logout and log back in. This problem does not occur with UltraVNC 1.0.2 or the latest version of TightVNC or RealVNC. Also, FYI, Mac OSX has a built in VNC cilent, you do not need to install Vine VNC unless you want per-user VNC sessions. Only TightVNC or UltraVNC 1.0.2 appear to be able to connect to the default OSX VNC server, the others fail.

Answer 2:
I don't to this in my environment, but in the Mac world the key should be Command-C to copy and Command-V to paste. Not sure if VNC client changes that or not...apparently it might given the answer above...but you might give it a shot.

Answer 3:
This may sound silly... but I don't use CTRL-C to copy... it does not work for me using TightVNC... I use ALT-C... that copies for me.

harrymc

Posted 2010-01-11T12:35:32.490

Reputation: 306 093

I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac. – sorin – 2010-01-27T21:08:51.223

Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution. – sorin – 2010-01-13T14:31:27.363

The solution is apparently using the latest version of TightVNC or RealVNC. – harrymc – 2010-01-13T15:09:11.017

4

As of 2018 (Mojave, High Sierra, etc) the VNC server is named /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd

If you can remotely log in, you can restart it with sudo killall screensharingd

The server restarts and resumes the previous connections.

DMPalmer

Posted 2010-01-11T12:35:32.490

Reputation: 141

1

This is fixed for me using Vine Server 4.01 on mac side and UltraVNC viewer 1.1.9.1 on windows side.

Default settings on server side produce the bug (very annoying).

To fix, open Vine Server preferences, Advanced tab, change Keyboard Events to User Session Events.

Happily using Ctrl+Ins/Shift+Ins for copy/paste in xcode now.

Note: this will likely break any keyboard remapper you have that relies on hardware events.

Eugene

Posted 2010-01-11T12:35:32.490

Reputation: 131