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 635475 - 2.12.1 disables all extensions
2.12.1 disables all extensions
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
2.12.x
Other Linux
: Normal major
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
: 638960 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-11-21 23:19 UTC by Christian Krause
Modified: 2011-01-08 14:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Krause 2010-11-21 23:19:56 UTC
If 2.12.1 is started by a newly created user, all extensions are disabled.

The same happens when upgrading from 2.12.0 to 2.12.1 if the user has never changed the extension settings. 

How to reproduce:
- clear all gthumb settings:
gconftool-2 --recursive-unset /apps/gthumb
- install/update to gthumb-2.12.1
- start gthumb
- check, whether the extensions are enabled

Current behavior:
- all extensions are disabled

Expected behavior:
- the default extensions should be enabled (gth-main.c:1215)
or
- when upgrading from 2.12.0 to 2.12.1: all extensions should be in the same state as they were before the update)

Comments:
- the issue is caused by commit: http://git.gnome.org/browse/gthumb/commit/?id=bed6cab99568b0fea7e6db4f11dc716c0640ff00

- the patch has the following problem:
* if /apps/gthumb/general/active_extensions was never set before, gconf will automatically return the default from the schemas file
* check the default value:
gconftool-2 --recursive-unset /apps/gthumb
gconftool-2 -g "/apps/gthumb/general/active_extensions"
[]
* this means, that the gconf library will not generate an error and so the "default_extensions" in gthumb/gth-main.c:1269 are never used
Comment 1 Paolo Bacchilega 2010-11-22 10:21:21 UTC
this should be fixed now, in master and in the gthumb-2-12 branch as well.
Comment 2 Matthias Hawran 2010-11-23 14:11:01 UTC
I can reproduce this bug with latest master so with the fix
(http://git.gnome.org/browse/gthumb/commit/?id=334055d7d391261b7ec95570d224cb8438995a94)

I'm on a fresh distro without any gthumb and with a fresh git master
Comment 3 Paolo Bacchilega 2010-11-23 18:51:26 UTC
does the command "gconftool-2 -g /apps/gthumb/general/active_extensions" return "[default]" for you after resetting the gconf keys with the command
"gconftool-2 --recursive-unset /apps/gthumb" ?
Comment 4 Matthias Hawran 2010-11-24 08:25:56 UTC
Yes 
gconftool-2 -g /apps/gthumb/general/active_extensions
returns
[default]

after executing
gconftool-2 --recursive-unset /apps/gthumb

Since this morning I cannot reproduce the bug... so I guess it's fixed...

Christian, is it fixed for you ?
Please close bug if so.
Comment 5 Christian Krause 2010-11-25 03:04:11 UTC
Paolo, Matthias, yes, commit http://git.gnome.org/browse/gthumb/commit/?id=7a50ad57332337bebdcaa0ae0fedbb138d63c37c fixes the issue for me.

Thank you very much for the quick response.
Comment 6 Michael Chudobiak 2011-01-08 14:39:10 UTC
*** Bug 638960 has been marked as a duplicate of this bug. ***