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 661779 - Nautilus crashes due to nautilus-open-terminal because this extension uses this function 'gconf_client_get_bool' a lot of time
Nautilus crashes due to nautilus-open-terminal because this extension uses th...
Status: RESOLVED FIXED
Product: nautilus-open-terminal
Classification: Other
Component: general
0.19
Other Linux
: Normal critical
: ---
Assigned To: Christian Neumair
Christian Neumair
Depends on:
Blocks:
 
 
Reported: 2011-10-14 15:44 UTC by Matthieu Baerts
Modified: 2011-10-17 11:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthieu Baerts 2011-10-14 15:44:50 UTC 
Hello,

This bug report is linked to this bug on launchpad: https://bugs.launchpad.net/ubuntu/+source/nautilus-open-terminal/+bug/869131

It seems Nautilus crashes nautilus-open-terminal uses a lot of time this function: 'gconf_client_get_bool'.
I'm not a specialist but I guess it's because this function is not "thread safe" (it seems nautilus crashes at random but it's always due to this same function: 'gconf_client_get') but it's maybe interesting to call this function only at the init and to use a 'gconf-listener' after that in order to know if a gconf key has changed.

I've added a patch (debdiff) to fix this bug but it's a workaround: https://launchpadlibrarian.net/82799919/nautilus-open-terminal_0.19-1build2ubuntu1.debdiff
Comment 1 Matthieu Baerts 2011-10-17 11:30:39 UTC 
It seems the issue is a double unref in ubuntuone-client-gnome not a gconf or nautilus-open-terminal issue => https://bugs.launchpad.net/bugs/865115
Sorry