Can you run gnucash under gdb with --g-fatal-warnings and find a stack trace for where the gconf message comes from in the gnucash code?
-derek Mark Johnson <[EMAIL PROTECTED]> writes: > In trying gnucash 2.0.2, I noticed that whenever I close a register, I > get the following two errors: > [EMAIL PROTECTED]:~$ gnucash > > (gnucash:27727): GConf-CRITICAL **: file gconf-listeners.c: line 444 > (ltable_remove): assertion `node != NULL' failed > > (gnucash:27727): GConf-CRITICAL **: file gconf-listeners.c: line 444 > (ltable_remove): assertion `node != NULL' failed > > This happens even if I simply open a register and immediately close it. > > I have reproduced it on two systems: > 1. Slackware 10.2 with gconf 2.6.2 > 2. Slackware 10.0 with gconf 2.14.0 > > In both cases, gnucash was built from source on the system where it was > running with that version of gconf installed prior to the build. > > The errors disappeared when I reverted system #2 to gnucash 2.0.1. > > Has anyone else noticed this problem? Was there something I should have > updated when I upgraded gnucash from 2.0.1 to 2.0.2? > > Mark > > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
