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 721590 - GSettings triggers all change callbacks of all GSettings objects
GSettings triggers all change callbacks of all GSettings objects
Status: RESOLVED DUPLICATE of bug 790640
Product: glib
Classification: Platform
Component: gsettings
2.38.x
Other Linux
: Normal major
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-01-05 18:02 UTC by Matt
Modified: 2017-11-20 22:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matt 2014-01-05 18:02:44 UTC
Hello,

After migrating to GSettings in MATE Desktop Environment, a mysterious bug (the "10 x-caja-windows" bug) was discovered. It occurs more often on slow machines when the ~/.config directory is not yet created.

The problem is that sometimes GSettings will trigger all change callbacks of all GSettings objects of an applications even if no parameters changed in any of the corresponding schemas. This leads to strange applications behaviours.

I wrote a example application that shows that the bug is somewhere in GSettings+DConf+Xsmp. https://github.com/LinuxMatt/Caja-bug170

The bug can be reproduced with gnome-session 3.x as well.

Regards,
Matt
Comment 1 Matt 2014-01-09 12:20:05 UTC
Some additional information:
- this often happens when no previous dconf user settings exist.
- it seems to be a race condition. Delaying the start of the program using GSettings prevents the problem from occuring most of the time.
Comment 2 Daniel Playfair Cal 2017-11-20 22:15:02 UTC
I assume this is the same issue: https://bugzilla.gnome.org/show_bug.cgi?id=790640
Comment 3 Philip Withnall 2017-11-20 22:38:09 UTC
(In reply to Daniel Playfair Cal from comment #2)
> I assume this is the same issue:
> https://bugzilla.gnome.org/show_bug.cgi?id=790640

Probably. Since you’ve got a backtrace, let’s dupe to bug #790640.

*** This bug has been marked as a duplicate of bug 790640 ***