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 98085 - Changes made in one instance of panel capplet is not visible in the other instance
Changes made in one instance of panel capplet is not visible in the other ins...
Status: RESOLVED DUPLICATE of bug 101064
Product: gnome-panel
Classification: Other
Component: general
2.0.x
Other other
: Normal minor
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-11-09 11:19 UTC by Andrew Sobala
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andrew Sobala 2002-11-09 11:19:19 UTC 
1. Invoke two instance of 'Panel preferences' capplet (Desktop preferences
   -> Advanced -> Panel)
2. Change the panel preferences in one instance of the capplet.
   (For eg : Uncheck the 'Close drawer when launcher is clicked' check box
    or change the 'Animation speed' to Fast)
3. The change will not be reflected in the other instance of the panel
   preferences capplet.
Comment 1 Andrew Sobala 2002-11-09 11:20:54 UTC 
Muktha, this came from bug 98079. You may want to add the Sun Cc:s
like you did to that bug.
Comment 2 Gregory Leblanc 2002-11-20 22:38:12 UTC 
Is there any good reason to allow invoking two copies of the panel
preferences dialogue?
Comment 3 Andrew Sobala 2002-11-20 22:53:11 UTC 
Yes and no. See bug 91853 and the usability mailing list for further 
discussion, but basically:

1) capplets should update if gconf changes
2) there should be "domains" within which multiple capplets aren't 
allowed.
Comment 4 Vincent Untz 2002-12-15 19:44:19 UTC 
I'm marking this bug as duplicate of bug #101064 because #101064 is
more generic (the problem is that the capplet doesn't listen for gconf
changes). The problem described here is a direct result of the problem
in #101064.

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