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 153948 - preload breaks the saved_state
preload breaks the saved_state
Status: RESOLVED DUPLICATE of bug 154005
Product: GConf
Classification: Deprecated
Component: gconf
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GConf Maintainers
GConf Maintainers
: 152868 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-09-28 13:20 UTC by Sebastien Bacher
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2004-09-28 13:20:03 UTC
* change the number of workspaces in the wnck-applet, notice it works
* "killall gconfd-2" or "kill -s HUP `pidof gconfd-2`"
* try to change the number of workspaces again -> does nothing

Some notes on the problem:
* grep metacity ~/.gconfd/saved_state
=> /apps/metacity is not listed. 

So when you SIGKILL or SIGHUP gconfd-2 the listener is not restored and you get
the breakage.

metacity (src/prefs.c) uses this:
  gconf_client_add_dir (default_client, "/apps/metacity",
                        GCONF_CLIENT_PRELOAD_RECURSIVE,
                        &err);

changing GCONF_CLIENT_PRELOAD_RECURSIVE with GCONF_CLIENT_PRELOAD_NONE fixes the
issue (/apps/metacity is listed in saved_state and the listener not broken).

So apparently something is wrong when using the preload ...

(gconf 2.8.0)
Comment 1 Vincent Untz 2004-09-30 13:47:37 UTC
*** Bug 152868 has been marked as a duplicate of this bug. ***
Comment 2 Elijah Newren 2004-10-29 14:54:00 UTC
Oddly enough, this is a duplicate of bug 154005.  The workspace switcher applet
(from num_workspaces_value_changed() in workspace-switcher.c) has libwnck send a
_NET_NUMBER_OF_DESKTOP message (in wnck_screen_change_workspace_count()) that
metacity catches (in event_callback() in display.c), metacity then changes the
number of workspaces using gconf (in meta_prefs_set_num_workspaces()), and then
metacity waits to get notification from gconf in order to actually change the
number of workspaces (in change_notify() in prefs.c).

It's kinda weird that Metacity knows the number of workspaces is changing, tells
gconf about it, and then waits for gconf to tell it in order to actually do
anything, but such is life I guess.

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