GNOME Bugzilla – Bug 616658
alarm / systray busted ...
Last modified: 2017-08-31 12:11:09 UTC
The setting "notify_with_tray" is being clobbered on every alarm daemon start. That is painful for two reasons: it dumps crud in ~/.gconf that we don't need, and it also turns this setting on un-conditionally on start [ which is exposed in the GUI, and we might want turned off - eg. for MeeGo which has no systray ]. So: from calendar/gui/alarm-notify/config-data.c: state = gconf_client_get_bool (conf_client, "/apps/evolution/calendar/notify/notify_with_tray", NULL); if (!state) /* Should be old client*/ { GSList *source; gconf_client_set_bool (conf_client, "/apps/evolution/calendar/notify/notify_with_tray", TRUE, NULL); source = gconf_client_get_list (conf_client, "/apps/evolution/calendar/sources", GCONF_VALUE_STRING, NULL); gconf_client_set_list (conf_client, key, GCONF_VALUE_STRING, source, NULL); So - we just set that boolean to TRUE if it is not set ? why ? Were we really just trying to detect that that key was not set ? And since that code dates back to oh - 2007 or before; can we just cut it out ? :-) Failing that, could we make it actually check for the key's non-existence rather than whether it is set to false ? I believe that can be done with gconf_client_get_without_default() - or something ? Thanks. [ I've patched this out for MeeGo ].
Please commit your MeeGo patch to master and gnome-2-32. Thanks in advance. I suppose it removes that "set to TRUE if off", which, I agree, shouldn't be there.
This is gone with the move to GSettings.