On Tue, Apr 17, 2007 at 09:06:27AM +0200, Andreas Bihlmaier wrote: > Tested on i386 + amd64 connecting to tightvnc server (running on a > windows box) works well, but there are some warnings issued: > > (tsclient:27333): Gtk-CRITICAL **: gtk_container_add: assertion > `GTK_IS_CONTAINER (container)' failed
I couldn't reproduce this exact error message, but I was able to find
that tsclient spit out an error message even when the called remote
control program (rdesktop, vncviewer) returned a 0 exit status (will
submit a patch upstream):
--- src/support.c.orig Sat May 20 17:43:29 2006
+++ src/support.c Tue Apr 17 22:42:48 2007
@@ -837,7 +840,7 @@ int tsc_launch_remote (rdp_file *rdp_in, int launch_as
*error = g_strdup(_("Failed to spawn.\nPlease verify your
installation."));
}
}
- if (std_err && strlen(std_err)) {
+ if (exit_stat && std_err && strlen(std_err)) {
g_warning ("\n%s\n", std_err);
if(error) {
*error = g_strdup((gchar*)std_err);
> Some settings (e.g. fullscreen) will fail if set with VNC, I guess wrong
> options
> are passed to vncviewer.
TightVNC needs -fullscreen. RealVNC uses -FullScreen. Patched for
TightVNC so it works with our ports system.
Please test.
Works for me on i386.
-ME
port-tsclient-0.148.tgz
Description: application/tar-gz
