You are not logged in.
had a tough time persuading google to give me meaningful results, so I share it:
when trying to connect via VNC to my girlfriend's macbook under leopard, I get this:
$ vinagre
The program 'vinagre' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadColor (invalid Colormap parameter)'.
(Details: serial 1724 error_code 12 request_code 1 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x7ffed491997c]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x15) [0x7ffed4919a15]
#2 /usr/lib/libX11.so.6 [0x7ffed83f24b0]
#3 /usr/lib/libX11.so.6(XESetCloseDisplay+0x43) [0x7ffed83d4783]
#4 /usr/lib/libGL.so.1 [0x7ffed8fb47b2]
GDK_GL_NO_STANDARD_COLORMAP=1 'fixes' it but makes it dead slow.
here's the debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477199
here's the gtk patch supposedly fixing it, from upstream:
--- branches/gtk-2-12/gdk/x11/gdkcolor-x11.c 2008/04/03 05:08:05 19969
+++ branches/gtk-2-12/gdk/x11/gdkcolor-x11.c 2008/04/03 05:11:06 19970
@@ -46,7 +46,7 @@
GdkColorInfo *info;
time_t last_sync_time;
- guint foreign : 1;
+ gboolean foreign;
};
#define GDK_COLORMAP_PRIVATE_DATA(cmap) ((GdkColormapPrivateX11 *) GDK_COLORMAP (cmap)->windowing_data)
@@ -107,7 +107,7 @@
gdk_colormap_remove (colormap);
- if (!private->screen->closed)
+ if (!private->screen->closed && !private->foreign)
XFreeColormap (GDK_SCREEN_XDISPLAY (private->screen), private->xcolormap);
if (private->hash)
@@ -1292,6 +1292,7 @@
private->screen = screen;
private->xcolormap = xcolormap;
private->private_val = FALSE;
+ private->foreign = TRUE;
colormap->size = visual->colormap_size;
but it doesn't work. bah.
ideas? (except using tightvnc)
Last edited by lloeki (2008-06-04 20:18:32)
To know recursion, you must first know recursion.
Offline
I'm using 32bit arch and having this issue as well
Offline
I tried to find a solution for this for a while but when I found it wasn't vinagre/gtk-vnc fault I left it alone. What really confuses me is that it occurs for me intermittently and when I reboot the issue disappears...
Edit: what do you mean the patch does not work. Did you rebuild everything (gtk2, gtk-vnc, vinagre) after applying it?
Last edited by Allan (2008-06-08 06:06:00)
Offline
I rebuilt and updated only gtk2, as it only applies to it. gtk-vnc and vinagre shouldn't need to be rebuilt.
it doesn't work as in same result.
To know recursion, you must first know recursion.
Offline