GnuCash 2.1.2 directions

[Christian Stimming]

If you want to discuss a bugzilla item, please keep this discussion on  
bugzilla. This is what this is for.

Quoting Wm Stewart <wstewart at livinginternet.com>:
> Can someone explain why this bug has been closed, ignored?  I honestly
> thought after my first notification of surreptitious external IP connection
> three months ago that this would have been considered seriously by the
> development team.  Rather disillusioning - not sure why I would report bugs
> in the future if they are going to be treated like this...
>
>    http://bugzilla.gnome.org/show_bug.cgi?id=407458#c14
>    Please advise (a) why would you close a bug that indicates something

1. You added your comments to the wrong bug: The initial report is  
about the gconf-editor program, not gnucash. And I already explained  
this in comment 10 but you didn't react on this.

2. The data that has been provided so far indicates to me this is a  
DUPLICATE of a known issue,  
http://wiki.gnucash.org/wiki/Windows#GConf.2FORBit_COMM_FAILURE , and  
this is being discussed in other bugzilla items already. Hence, this  
bug must be closed to avoid duplicated discussions.

3. If you think you have discovered a bug that is not yet covered by  
the bug numbers mentioned in that wiki page, please file this as a  
*new* item. Thanks.

Christian