« Return to Thread: tightvnc server on Unix

[VNC] RE: tightvnc server on Unix

by Arfin Greebly :: Rate this Message:

Bob,

Not long ago (a few months) I upgraded my desktop at work from Ubuntu 8.x
to Ubuntu 10.x and part of that package was KDE 4.

I had been using VNC for years on this box without any problems.
Evidently, however, some bright spark in the Ubuntu/KDE development camp
thought that it would be a stellar idea to incorporate display zero (the
primary desktop) into the RFB support -- /as the default/. This
immediately broke TightVNC. I could no longer establish a VNC session
that did not affect ":0" in some way. I would start vncserver as display
:21, and then try to launch a program (like kmail or Firefox) and the
program would pop up on the primary display ( :0 ) instead of display :21.
Graphics support for non-zero display sessions became nearly unusable.

I was able to mostly solve the problem by abandoning KDE and going with
Gnome. Graphics support was still spotty, and was never fully resolved,
but the remote session was usable.

The idea of being able to use VNC with display:0 is occasionally
attractive, and clearly has its uses. Implementing that feature so that
it breaks the ability to use multiple non-zero display sessions is simply
bad engineering.

If I want to share a desktop with someone else, I just open a shareable
display session, for example as display:33, and then I log into :33 along
with whomever will be sharing it, and do the collaboration there.

I would much rather sacrifice having VNC available for display:0 than lose
the ability to support multiple non-zero displays.

~~ Garry

----- On Tue, 6 Mar 2012, Bob McConnell wrote: -----

>>
>> From: Constantin Kaplinsky
>>
>>>>>>> Yossi Itzkovich wrote:
>>
>>> It seems that the tight vnc C++ code is old. It uses X11R3, and no
>>> news about it in the "What's new" section for long time.
>>>
>>> Is there a good reason for it ?
>>
>> We did not work on TightVNC for *nix for a long time -- version for Windows
>> was our #1 priority. However, it's VERY likely that we'll return to *nix
>> development later this year.
>
>
>
> The primary issue with the Unix server is that it can't open the current desktop session. It always creates a new session for you. I have been using x11vnc as my server on XFCE/Slackware desktops.
>
> Bob McConnell
>
>
> ------------------------------------------------------------------------------
>

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___________________________________________________________
TightVNC mailing list, VNC-Tight-list@...
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

« Return to Thread: tightvnc server on Unix