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 344630 - gconf key doesn't match between source code and schema
gconf key doesn't match between source code and schema
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-06-12 09:00 UTC by Wang Xin
Modified: 2006-06-12 11:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
patch to fix the bug (2.28 KB, patch)
2006-06-12 09:11 UTC, Wang Xin 		committed Details | Review

Description Wang Xin 2006-06-12 09:00:24 UTC 
Please describe the problem:
In schema, a gconf key called confirm_expunage is created and in calendar/gui/migration.c ConfirmExpunge is migrated to confirm_expunge. But in source code, confirm_purge is used, everytime one wants to get the value of confirm_purge key, FALSE is returned. So when one wants to purge a tasklist, no confirm would popup.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Wang Xin 2006-06-12 09:11:36 UTC 
Created attachment 67160 [details] [review]
patch to fix the bug
Comment 2 Harish Krishnaswamy 2006-06-12 10:07:23 UTC 
Looks good to commit.
Comment 3 Wang Xin 2006-06-12 10:12:00 UTC 
Can i commit the patch into gnome-2-14 branch too?
Comment 4 André Klapper 2006-06-12 10:54:48 UTC 
since there are no user visible strings affected and this does not change the API, i'd say yes - please commit to gnome-2-14 too. thanks in advance
Comment 5 Harish Krishnaswamy 2006-06-12 11:56:17 UTC 
Committed on both branches - so this could get in time for today's relase. Thanks for the patch.