GNOME Bugzilla – Bug 666442
assertion `listener->priv->window != NULL' failed
Last modified: 2012-02-26 12:13:19 UTC
Steps to reproduce: 1. Remote->Reverse Connections->Enable reverse connections 2. Attach a client The connection is immediately closed and the following appears on stderr: ** (vinagre:16076): CRITICAL **: incoming: assertion `listener->priv->window != NULL' failed
Created attachment 203787 [details] backtrace
(In reply to comment #1) > Created an attachment (id=203787) [details] > backtrace Starting program: /tmp/vinagre/vinagre/vinagre [Thread debugging using libthread_db enabled] [New Thread 0x7fffedfa1700 (LWP 8841)] [New Thread 0x7fffe291a700 (LWP 8842)] [New Thread 0x7fffe1ae8700 (LWP 8843)] ** CRITICAL **: vinagre_cmd_direct_connect: assertion `VINAGRE_IS_WINDOW (window)' failed Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x0, log_level=<optimized out>, format=0x7ffff580b512 "%s: assertion `%s' failed", args1=0x7fffffffd678) at /build/buildd/glib2.0-2.30.2/./glib/gmessages.c:577 577 /build/buildd/glib2.0-2.30.2/./glib/gmessages.c: No such file or directory. in /build/buildd/glib2.0-2.30.2/./glib/gmessages.c (gdb) thread apply all bt
+ Trace 229293
Thread 1 (Thread 0x7ffff7fc8940 (LWP 8840))
Created attachment 203788 [details] backtrace Sorry, previously I posted the wrong backtrace (obtained removing the assertion).
Created attachment 203791 [details] [review] set the window on the reverse vnc listener It looks like the window was never set on the reverse VNC listener object. Can you test the patch, and let me know if it fixes the problem for you?
Perfect, thanks! Works like a charm. Will the fix be applied just to the master trunk or will you make also a new 3.2.x release?
Comment on attachment 203791 [details] [review] set the window on the reverse vnc listener Thanks for testing the patch. I pushed it to the gnome-3-2 and master branches as commit d74df1bc99d1bec553d72cad9c7b5f9a3ff60020 and e8052a5d7ef313b89a856b45aee933e20fddd3dc. There is not normally a .3 stable release, but there have been enough changes and fixes that this is now worthwhile, so I will probably make one next week.
*** Bug 670804 has been marked as a duplicate of this bug. ***