GnuCash 2.1.2 directions

[Christian Stimming]

Am Montag, 27. August 2007 20:04 schrieb Wm Stewart:
> Hi folks, I just updated this bug, am concerned about installer virus
> contamination, perhaps not from GNUCash but from included code, but in any
> case seems to be the only explanation:
>
> http://bugzilla.gnome.org/show_bug.cgi?id=407458

Errr... no, that's really very unlikely; there are just way too many existing 
bugs in the so that any malfunctioning would actually require something like 
a virus or similar. Maybe the system itself has one? Certainly this is not at 
all "the only explanation".

But seriously: Please note that the original bug  (CORBA/COMM_FAILURE:1.0) has 
been known for a long time by now, see 
http://wiki.gnucash.org/wiki/Windows#GConf.2FORBit_COMM_FAILURE and 
references therein.

On the other hand, we are open for any substantiated research in that area. 

Christian

> Wm Stewart wrote:
> > Perhaps you could test installation of 2.1.2 on a new Windows machine
> > with a firewall that traps outgoing connections as well as incoming?  You
> > are right that there are a lot of connections to itself through 127.0.0.1
> > or the machine IP, which I allowed, and the one external connection
> > attempt.
> >
> > On the tests I've done on two machines, denying the external connection
> > on GnuCash start-ups led to the error message, and once the connection
> > was allowed the error went permanently away.  Interestingly, subsequent
> > repeated deinstalls and reinstalls failed to replicate the external
> > connection attempt or the error message on either machine, indicating the
> > issue occurs only on machines that have never had GnuCash previously
> > installed.
> >
> > Derek Atkins wrote:
> >> Hmm..  I have no idea why it would attempt to contact that address.
> >> It's nothing to do with us, that's for sure.
> >>
> >> -derek
> >>
> >> Quoting Wm Stewart <wstewart at livinginternet.com>:
> >>> Afaik I do not have anything to do with llnw.net.  My machines have
> >>> addresses like 209.217.x.x.
> >>>
> >>> Derek Atkins wrote:
> >>>> 68.142.91.87 resolves to:
> >>>>
> >>>>  87.91.142.68.in-addr.arpa domain name pointer cds192.lga.llnw.net.
> >>>>
> >>>> What's your host's IP Address?
> >>>>
> >>>> -derek
> >>>>
> >>>> Quoting Wm Stewart <wstewart at livinginternet.com>:
> >>>>> Hi, reinstalling did not replicate the error, but starting on a new
> >>>>> machine
> >>>>> does.  On the new machine, the error went away once I allowed what
> >>>>> ZoneAlarm identified as gnucash-bin.exe to access IP 68.142.91.87.
> >>>>>
> >>>>> Derek Atkins wrote:
> >>>>>> I can't imagine it's trying to contact any gnucash website.  We
> >>>>>> certainly have not told it to.  It's possible that it's trying to
> >>>>>> ask the network for other gconf instances via a broadcast address
> >>>>>> to the local network.
> >>>>>>
> >>>>>> -derek
> >>>>>>
> >>>>>> Wm Stewart <wstewart at livinginternet.com> writes:
> >>>>>>>    b.  I searched on the text of the bug and found it seems to also
> >>>>>>> occur
> >>>>>>> with a variety of other applications:
> >>>>>>> http://www.google.com/search?hl=en&q=%22An+error+occurred+while+loa
> >>>>>>>ding+or+saving+configuration+information%22&btnG=Google+Search