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 335892 - error dialog when opening preferences if settings are read-only
error dialog when opening preferences if settings are read-only
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 335923
 
 
Reported: 2006-03-24 21:25 UTC by Jeffrey Stedfast
Modified: 2021-05-19 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Jeffrey Stedfast 2006-03-24 21:25:27 UTC
if you open the preferences dialog after setting all of the mailer gconf keys
read-only, you get an error dialog from gconf, saying:

Can't overwrite existing read-only value: Can't overwrite existing read-only
value: Value for `/apps/evolution/mail/display/fonts/use_custom' set in a
read-only source at the front of your configuration path

this suggests what is probably happening is that evo is reading the setting from
gconf and then setting the value on the preferences widget after the prefs
widget has been hooked up to a signal handler which tries to re-save the setting
when the widget changes.

if that's the case, then it should be fixable by setting the original value
before hooking up the callback

Other information:
Comment 1 Matthew Barnes 2008-03-11 00:27:03 UTC
Bumping version to a stable release.
Comment 2 André Klapper 2021-05-19 12:14:21 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.