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 90788 - cddb-slave2-properties capplet should instant-apply preference changes
cddb-slave2-properties capplet should instant-apply preference changes
Status: RESOLVED FIXED
Product: gnome-media
Classification: Deprecated
Component: CDDBSlave2
2.0.x
Other Linux
: Normal minor
: ---
Assigned To: gnome media maintainers
gnome media maintainers
: 90790 (view as bug list)
Depends on:
Blocks: 90790 116366
 
 
Reported: 2002-08-15 00:57 UTC by Ben Liblit
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch to fix the problem (1.27 KB, patch)
2003-06-09 12:25 UTC, Kjartan Maraas 		none Details | Review

Description Ben Liblit 2002-08-15 00:57:46 UTC 
The CDDB settings control panel (cddb-slave2-properties) does not instantly
apply settings changes.  Instead, settings are only updated when the user
presses the "Apply" button.  If the user presses "Close" instead, changed
settings are not stored back into gconf.
Comment 1 Iain 2002-09-23 11:48:21 UTC 
Marking as minor as nobody knows about this dialog due to Seth's
boycotting of it.
Comment 2 David Kennedy 2002-11-23 16:23:57 UTC 
Not sure if this kind of change is not allowed due to the feature
freeze. If so, the two GNOMEVER keywords can be replaced with a
GNOMEVER2.3.

The capplet is present in both 2.0 and 2.1 - should the severity be
raised?
Comment 3 Luis Villa 2002-11-25 19:04:49 UTC 
there's still a week of ui-slush flex available, but it's unlikely
this is going to be done.
Comment 4 Christian Kellner 2003-03-24 20:55:22 UTC 
This bug is still present in gnome 2.2 (debian/unstable).
So I am changing the GNOMEVER keyword to "GNOMEVER2.2".
Comment 5 Kjartan Maraas 2003-06-09 12:25:07 UTC 
Is this the way to fix this?
Comment 6 Kjartan Maraas 2003-06-09 12:25:33 UTC 
Created attachment 17345 [details] [review]
patch to fix the problem
Comment 7 Kjartan Maraas 2003-07-08 07:43:40 UTC 
There's an updated patch in #116804. It's really just the first line
of this (and the other) patch that applies to this bug.
Comment 8 Luis Villa 2003-07-11 01:26:31 UTC 
*** Bug 90790 has been marked as a duplicate of this bug. ***
Comment 9 Luis Villa 2003-07-11 01:27:01 UTC 
Adding the PATCH keyword.
Comment 10 Ted Gould 2003-07-16 07:47:42 UTC 
This fix was included in the patch for bug 116804.  That one has been
applied, so this bug should be fixed.  I'm marking the bug as fixed.