Re: [Tigervnc-devel] New portable vncviewer

It may contain the source for the tight decoder, but that encoding is not exposed in the GUI. The GUI still behaves pretty much exactly like RealVNC. On 3/16/11 1:49 AM, Martin Koegler wrote: > On the other hand, the TigerVNC java viewer is based on Tightvnc [some > files are even carring such a

Re: [Tigervnc-devel] Refresh issue with GnuTLS and status of beta

On 03/15/2011 08:29 PM, DRC wrote: > On 3/15/11 4:48 AM, Sebastiaan Breedveld wrote: >> 1) The new vncserver script does something weird with -fg. When I use >> this switch, xfce4 refuses to start with: >> >> "Unable to contact settings server. Failed to connect to socket >> /tmp/dbus-GBOh4ZTlHF:

Re: [Tigervnc-devel] RHEL4 legacy build?

I get identical results with the 1_1 branch. Can anyone else verify this? Thanks, -brian On Tue, Mar 15, 2011 at 1:49 PM, Brian Hinz wrote: > Ah, hadn't seen that... I'll try that and let you know. > > Thanks, > -brian > > > On Tue, Mar 15, 2011 at 1:38 PM, DRC wrote: > >> The trunk is quite

Re: [Tigervnc-devel] RHEL4 legacy build?

I do all of my pre-release builds on CentOS 4.8. Can you try my binaries? http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases These are built using gcc4/g++4 and the Xorg 7.4 code base (unix/build-xorg -version 7.4) On 3/16/11 10:32 AM, Brian Hinz wrote: > I get identical results with t

[Tigervnc-devel] New pre-beta build

http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases -- Reverts default behavior of vncserver but adds a 'vncserver -autokill' option that will automatically kill Xvnc whenever xstartup exits. -- Colocation vs. Man

Re: [Tigervnc-devel] New pre-beta build

On Wed, 16 Mar 2011 15:50:53 -0500, DRC wrote: > http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases [1] > > -- Reverts default behavior of vncserver but adds a 'vncserver > -autokill' option that will automatically kill Xvnc whenever xstartup exits. How does this interact with the "

Re: [Tigervnc-devel] RHEL4 legacy build?

Thanks. Do you have issues with the x86_64 build? I had to grab the autoconf macros for pkg-config from RHEL5 because PKG_CHECK_EXISTS isn't provided with the older version shipped with RHEL4. I also had to build with NASM=/usr/bin/yasm (no big deal, but could be part of the problem?) This was

Re: [Tigervnc-devel] RHEL4 legacy build?

Works great. Is there anything that you've done differently or non-standard packages in your build env? On Wed, Mar 16, 2011 at 4:49 PM, DRC wrote: > I do all of my pre-release builds on CentOS 4.8. Can you try my binaries? > > http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases > > The

Re: [Tigervnc-devel] New pre-beta build

-once shuts down Xvnc after the first VNC connection has disconnected. It only works when Xvnc is run from inet.d (it's designed to be used to launch Xvnc on demand as a connection comes in.) -autokill is a fundamentally different feature. -autokill is a function of the vncserver startup script,

Re: [Tigervnc-devel] RHEL4 legacy build?

YASM is probably the largest part of your problem. It is known not to produce correct code when building the 64-bit version of libjpeg-turbo. Earlier versions of NASM had the same problem (you have to use NASM 2.05 and later.) Read BUILDING.txt for instructions on how to build a NASM 2.05 RPM fr

Re: [Tigervnc-devel] New portable vncviewer

Here's the source repo for the java viewer that I've been working on: https://bphinz.svn.cvsdude.com/vncviewer/ Have a look and let me know what you think. I'm going to start working on fi