tigervnc: Missing /opt/local/bin/Xvnc

[wdn@…]

I just installed tigervnc from MacPorts on my MacBook Pro running Snow Leopard. When I execute the following command:

vncserver -geometry 1920x1200 :90

I receive the following error message:

vncserver: couldn't find "/opt/local/bin/Xvnc".

I could not find any record of this problem in the current tickets.

Thanks,

Dave

[ryandesign (Ryan Carsten Schmidt)]

And does /opt/local/bin/Xvnc exist on your system?

[wdn@…]

Replying to ryandesign@…:

And does /opt/local/bin/Xvnc exist on your system?

No it does not. But the installation process for tigervnc seemed to go fine and did not complain about any build failures or unresolved package dependencies. How should I proceed?

Thanks,

Dave

[ryandesign (Ryan Carsten Schmidt)]

Ok, I see the same on my system. I guess we're not actually building Xvnc. My brief research shows it to be a very convoluted process to do so, including the need to download, extract, rearrange and patch the xorg-server source. You can see ​how slackware is doing it (see the parts "Move the xorg-server sources into the TigerVNC tree" and "* Building xserver *"). If someone wanted to dissect that and turn it into Portfile modifications I'm sure we'd welcome that. We may want to make the tigervnc server a separate port from the existing one, so that users who only want the client don't need to spend time downloading the xorg-server source and building the tigervnc server.

I assume the vnc server already built into OS X is not suitable for your needs?

[wdn@…]

I am new to Macs with most of my experience in the Linux environment. So I do not know how well the vnc server built into OS X works for my needs. Nor do I know how to access it. Before downloading tigervnc via Macports, I checked to see if vncserver and vncviewer were available in my path. Since I did not find them, I assumed vnc must be an add on via Macports or one of the other package environments. There were several versions of vnc available through Macports including cots, realvnc, tigervnc and tightvnc. I chose tigervnc because it is what is used in Fedora linux distros and I will be interacting with several linux systems via my Mac. But perhaps tightvnc or realvnc would work as well. I'm not sure. I use tightvnc on a Windows laptop and that seems to work well.

Do you have any advice on how to proceed? It does not look like a fix for tigervnc will happen very quickly.

Thanks,

Dave

[wdn@…]

I'm not having much success with the other vnc port packages such as cotsvnc, tightvnc, and vnc. Would be nice if tigervnc could be made to work.

[wdn@…]

What is the status of this ticket? Is there any chance that this will be worked on?

[jmroot (Joshua Root)]

Replying to wdn@…:

What is the status of this ticket? Is there any chance that this will be worked on?

The ticket is open. As the tigervnc port has no maintainer, an interested party would need to provide a patch for this to be fixed.

[xverges@…]

Cc Me!

[cooljeanius (Eric Gallager)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to wdn@…:

I am new to Macs with most of my experience in the Linux environment. So I do not know how well the vnc server built into OS X works for my needs. Nor do I know how to access it. [snip]

The VNC server in OS X can be turned on by opening System Preferences, going to Sharing, turning on Screen Sharing, then clicking Computer Settings and enabling the checkbox "VNC viewers may control screen with password" and entering a password.

The VNC client in OS X can be accessed by typing a vnc:// URL into a web browser, or giving such a URL to the open command in the Terminal, or by manually launching /System/Library/CoreServices/Screen Sharing.app.

[ryandesign (Ryan Carsten Schmidt)]

I now maintain the tigervnc port.

[ryandesign (Ryan Carsten Schmidt)]

The tigervnc port no longer provides the vncserver program, only the vncviewer program.