taresus: I am unable to reproduce your issue. Interacting with the column separator doesn't even touch linuxdcpp code, it would be internal to gtk+. You can try disabling accessibility as mentioned in bug #437426.
As for the other issue, it appears to be a deadlock between thread 1 & 10. A call to gdk_flush() seems to be waiting indefinitely while the main thread is waiting for the gdk lock to be returned by thread 10. As for why gdk_flush() is not returning, I've no idea. Gdk explicitly recommends calling gdk_flush in such situations (http://library.gnome.org/devel/gdk/unstable/gdk-Threads.html):
"Before calling gdk_threads_leave() from a thread other than your main thread, you probably want to call gdk_flush() to send all pending commands to the windowing system."
taresus: I am unable to reproduce your issue. Interacting with the column separator doesn't even touch linuxdcpp code, it would be internal to gtk+. You can try disabling accessibility as mentioned in bug #437426.
As for the other issue, it appears to be a deadlock between thread 1 & 10. A call to gdk_flush() seems to be waiting indefinitely while the main thread is waiting for the gdk lock to be returned by thread 10. As for why gdk_flush() is not returning, I've no idea. Gdk explicitly recommends calling gdk_flush in such situations (http:// library. gnome.org/ devel/gdk/ unstable/ gdk-Threads. html):
"Before calling gdk_threads_leave() from a thread other than your main thread, you probably want to call gdk_flush() to send all pending commands to the windowing system."
So, in summary: I hate you GTK+....