Call GTK functions without gdk lock
Bug #797188 reported by
Yehouda
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| AppMenu GTK+ |
Fix Released
|
Medium
|
Allison Karlitskaya | ||
| Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
There are calls to GTK functions without a gdk lock, which cause "random" crashes on mullti-threaded applications.
The one that we hit is the call to
dsubmenu_
find_menu_bar
...
rebuild_
do_rebuild
<glib stuff>
It is because is called vi g_timeout_add inside rebuild, which doesn't deal with gdk lock.
It should call gdk_threads_
We found the bug running on Linux Mint.
As a work around we setenv UBUNTU_MENUPROXY to nothing.
Other iseas?
Related branches
lp:~desrt/appmenu-gtk/gdkthreads-fix
- Charles Kerr (community): Approve
-
Diff: 13 lines (+1/-3)1 file modifiedsrc/bridge.c (+1/-3)
lp:~indicator-applet-developers/ubuntu/precise/appmenu-gtk/upstream
- Ken VanDine: Pending requested
-
Diff: 19287 lines (+9555/-8822)28 files modifiedINSTALL (+7/-2)
Makefile.am (+3/-1)
Makefile.am.coverage (+48/-0)
Makefile.in (+73/-27)
aclocal.m4 (+5/-5)
build/autotools/libtool.m4 (+0/-8001)
build/autotools/ltoptions.m4 (+0/-384)
build/autotools/ltsugar.m4 (+0/-123)
build/autotools/ltversion.m4 (+0/-23)
build/autotools/lt~obsolete.m4 (+0/-98)
compile (+183/-16)
config.guess (+31/-18)
config.sub (+39/-26)
configure (+313/-12)
configure.ac (+16/-3)
debian/changelog (+9/-0)
depcomp (+66/-8)
install-sh (+18/-11)
m4/gcov.m4 (+86/-0)
m4/libtool.m4 (+8001/-0)
m4/ltoptions.m4 (+384/-0)
m4/ltsugar.m4 (+123/-0)
m4/ltversion.m4 (+23/-0)
m4/lt~obsolete.m4 (+98/-0)
missing (+4/-49)
src/Makefile.am (+4/-0)
src/Makefile.in (+20/-12)
src/bridge.c (+1/-3)
Revision history for this message
| Bilal Akhtar (bilalakhtar) wrote | #1 |
Revision history for this message
| Bilal Akhtar (bilalakhtar) wrote | #2 |
Revision history for this message
| Yehouda (yeh-lispworks) wrote | #3 |
Revision history for this message
| Olli Ries (ories) wrote | #4 |
| Changed in appmenu-gtk: | |
| status: | New → Incomplete |
| importance: | Undecided → Medium |
| assignee: | nobody → Ryan Lortie (desrt) |
Revision history for this message
| Allison Karlitskaya (desrt) wrote | #5 |
| affects: | gtk+3.0 (Ubuntu) → ubuntu |
| Changed in ubuntu: | |
| status: | New → Invalid |
Revision history for this message
| Allison Karlitskaya (desrt) wrote | #6 |
| Changed in appmenu-gtk: | |
| status: | Incomplete → New |
| Changed in appmenu-gtk: | |
| status: | New → Fix Committed |
| description: | updated |
| Changed in appmenu-gtk: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
From what it appears, this seems to be a bug with the ubuntumenuproxy part of Ubuntu's patched GTK source.