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 487064 - get rid of /apps/ekiga/general/version
get rid of /apps/ekiga/general/version
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: general
unspecified
Other All
: Low enhancement
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-16 07:31 UTC by Kilian Krause
Modified: 2009-01-09 10:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kilian Krause 2007-10-16 07:31:38 UTC 
Please describe the problem:
As stated in http://bugs.debian.org/446689 the GConf key still has the old value after completing the druid. Damien already agreed on IRC this is cruft from the old days where GConf was unreliable (like the SCHEMA_AGE). This is just a reminder bug only to have both of these checks removed. If there's an SVN commit suitable for backporting to 2.0.11 I'd welcome to add this to Debian.

Steps to reproduce:
1. set /apps/ekiga/general/version to 2009
2. start ekiga, complete the druid
3. read /apps/ekiga/general/version (it's not updated to 2011)


Actual results:
The config druid keeps re-appearing each time.

Expected results:


Does this happen every time?


Other information:
Comment 1 Damien Sandras 2007-10-16 10:26:45 UTC 
I tried several times here and the value is correctly updated.

I doubt there is a bug there.

If you look at the code in src/gui/druid.cpp, function finish_cb () :

  /* Update the version number */
  version = MAJOR_VERSION*1000+MINOR_VERSION*10+BUILD_NUMBER;
  gm_conf_set_int (GENERAL_KEY "version", version);

The only reason why this code would not be executed is if the druid is cancelled. But if the user clicks on Finish, the code will be executed.

I keep the bug open because we will improve the system, but the behavior you describe is probably not correct.
Comment 2 Matthias Schneider 2008-10-13 06:24:38 UTC 
Is this still valid for 3.0.0 ? We dont even have a druid anymore...
Comment 3 Damien Sandras 2008-10-14 17:56:13 UTC 
yes it is still valid. We have an assistant.
Comment 4 Eugen Dedu 2009-01-09 10:04:14 UTC 
With the removal of SCHEMA_AGE, is this bug still valid?
Comment 5 Damien Sandras 2009-01-09 10:22:22 UTC 
Indeed not.