Re: [Bug 1046805] Re: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full

> > Yehouda, has this bug been fixed for you? > I don't know. It doesn't bother us, because we don't use this input method, but it hits users of our software. We tell them to set GTK_IM_MODULE to something so it doesn't use ibus, that works around it and the

[Bug 910602] Re: unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast() from menu_item_is_activating() from close_in_idle()

Why is this marked as fixed? The code in http://bazaar.launchpad.net/~dbusmenu-team/dbusmenu/trunk.12.10/view/head:/libdbusmenu-gtk/client.c is still broken, using g_idle_add to schedule a function close_in_idle that calls GTK functions, so i still calls GTK functions without a lock, which is

[Bug 1046805] Re: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full

It is now marked as fixed in the ibus project. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046805 Title: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_thread

[Bug 1046805] Re: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full

The trunk is being fixed in https://codereview.appspot.com/6488104/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046805 Title: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in

[Bug 1046805] Re: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full

Will affect ibus-gtk3 too ** Package changed: ubuntu => ibus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046805 Title: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in

[Bug 1046805] [NEW] X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full

Public bug reported: This is a bug in ibus-gtk2 version 1.4, libray /usr/lib/x86_64-linux- gnu/gtk-2.0/2.10.0/immodules/im-ibus.so is in Ubuntu 12.04. It causes "random" X IO errors , because it is a multithreading bug. I reported it already to the ibus project at http://code.google.com/p/ibus/

[Bug 910602] Re: unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast() from menu_item_is_activating() from close_in_idle()

Looking at it closer, it maybe that submenu_notify_visible_cb needs to ref the argument to close_in_idle (and close_in_idle deref). but it certainly neds the ggdk lock too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.l

[Bug 910602] Re: unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast() from menu_item_is_activating() from close_in_idle()

I think the reason for the crash is that close_in_idle is called without a GDK lock. It is setup by submenu_notify_visible_cb in /libdbusmenu- gtk/client.c using g_idle_add. It probablu needs to use gdk_threads_add_idle instead. There is certainly a problem in parse.c, where watch_menu uses

[Bug 797188] Re: Call GTK functions without gdk lock

We didn't try on GTK 3. We don't run our software on GTK 3 at all at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797188 Title: Call GTK functions without gdk lock To manage notificat

[Bug 637151] [NEW] Hanging because of a bug in GTK (629277)

Public bug reported: GTK has this bug in 2.18 and 2.20: https://bugzilla.gnome.org/show_bug.cgi?id=629277 It causes hanging, and because it is a low-level bug it is difficult to work around it. It is already fixed in the master branch of GTK, but needed to be included in the distribution as so