After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 156885 - eel is not thread safe
eel is not thread safe
Status: RESOLVED WONTFIX
Product: eel
Classification: Deprecated
Component: general
unspecified
Other FreeBSD
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-10-30 10:18 UTC by Jean-Yves Lefort
Modified: 2011-09-22 04:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fixes thread safety bugs (1.11 KB, patch)
2004-10-30 10:18 UTC, Jean-Yves Lefort 		none Details | Review
patch updated for 2.10.0 (2.51 KB, patch)
2005-03-21 05:50 UTC, Jean-Yves Lefort 		none Details | Review

Description Jean-Yves Lefort 2004-10-30 10:18:19 UTC 
eel is not thread safe, because in several places the GDK lock is not held while
calling GTK+ from a main loop callback. Patch is attached.
Comment 1 Jean-Yves Lefort 2004-10-30 10:18:46 UTC 
Created attachment 33247 [details] [review]
fixes thread safety bugs
Comment 2 Jean-Yves Lefort 2005-03-21 05:50:45 UTC 
Created attachment 38997 [details] [review]
patch updated for 2.10.0
Comment 3 Christian Kirbach 2007-10-13 13:13:45 UTC 
Thanks for supplying a patch. It is a shame nobody took a look.

Is eel head still not thread-safe?
Comment 4 Akhil Laddha 2011-09-21 09:51:11 UTC 
eel as a standalone product is no longer maintained. However, large parts of eel was imported into the eel sub directory in nautilus.

Can you please check again whether this issue still happens in nautilus 3.0.2 or upcoming nautilus 3.2.0 and update this report by adding a comment so that the bug can be reassigned to nautilus if it's still valid.
Comment 5 Cosimo Cecchi 2011-09-22 04:16:50 UTC 
Not relevant anymore for Nautilus.