Error Code: 2.115
Often when I'm attempting to connect to a manually configured VNC connection I'll get Error Code 2.115. I don't have a keyboard or mouse connected to the computer so without the VNC connection I can't control anything and just have to force a reboot. After that I can connect without any issues. I've searched, but haven't found any details about this error or how to prevent it. Any suggestions?
-
Hey folks. Can you please send your Jump Desktop logs from the Android device? That might help us understand whats going on: Reproduce the problem and then go back to Jump's main screen and tap the settings icon on the top left. Then in the Diagnostics section tap the "Send Log" row. -
Wow, surprised no-one figured this out yet. I did after reading some connection logs. Your rfbversion in jump has to be old. Once I specified -rfbversion 3.6 on server it does coming up with the can't connect 2.115 error. Makes me wonder bout jump even more after their stupid gui got overhauled and annoying now. The stupid keyboard button method they use now sucks I have to hit it 3x to get the command ribbon and keyboard on screen at same time. Junk keeps slowly getting worse, ugh (sucks cause they got the mouse handling right unlike everyone else). -
No I did not mean my app install was old I meant the rfb protocol stack being used within jump must be older than current. I'm using most current x11vnc server on my xubuntu 14.04 server. I did just reinstall my OS which was roughly 2 years old and even though x11vnc had updated before I reinstalled older files retained during update must have helped that keep going.
If you install x11vnc today you'll most likely have this problem (it's random and can take couple hours to start acting up, but it'll happen).
So, to fix this whatever command chain you use to start x11vnc (and probably any vnc server as rfb*commands are core vnc commands and not server specific) just add -rfbversion 3.6 (I stuck it in the middle with other rfbport and rfbauth switches, but really shouldn't matter).
Also of note I use a sysinit script in /etc/init titled vnc0.conf so I can issue sudo service vnc0 restart when needed (and comes in handy as this starts independent of my LightDM xwindows manager meaning I don't need to login before vnc runs and I can even login to my Linux box via vnc).
Last note if you get this error service restart on vnc didn't help but I could issue sudo service lightdm restart (either via ssh or ctrl+ alt+f2 (any other console besides the one running your desktop) if you run command from within lightdm it won't fully restart as you're actively using it. All this does is same as logging out and back in so save any open files beforehand.
Hope all that helps. Even though I use xubuntu I believe this should written with -
Written with= work with any version of Ubuntu (may need to sub your website manager service name in if not urging lightdm (anyone using any version of Ubuntu other than xubuntu should migrate over it runs almost exactly like Ubuntu except no unity and it is very light on system resources (I run it on old netbooks even!!) Without sacrificing anything functionality, performance or otherwise.
Icing on the cake is it's very Windows like (taskbar and tray on top of display instead of bottom) so even newbie or say computer stupid people who swear by Windows will find this the easiest Linux most likely to start on (and again not sacrificing anything so even guru users like myself get the full *nix they like). Did I mention xubuntu is free?! I do recommend trying out 14.04 first and not 15 or 16 as of writing this. -
Such errors code looking like Sign In 0x87dd0006 that should be recovered by them only. From this site, they can get fruitful advice.
Please sign in to leave a comment.
Comments
11 comments