Re: GnuCash 2.1.2 directions

Hi... please don't shoot the messenger - I found the same problem in the 2.2.1 install as well, and have written it up here with screen shots: http://bugzilla.gnome.org/show_bug.cgi?id=363648#c21 Please let me know if that is the wrong place for this bug or if there is a better place. Nathan Buc

Re: GnuCash 2.1.2 directions

Nathan Buchanan wrote: > On 8/31/07, *Patrik Lermon* <[EMAIL PROTECTED] > > wrote: > > On 8/31/07, Wm Stewart <[EMAIL PROTECTED] > > wrote: > > > > Good problem solving - however two issues: > > > >* You used V2.2.1 w

Re: GnuCash 2.1.2 directions

On 8/31/07, Patrik Lermon <[EMAIL PROTECTED]> wrote: > > On 8/31/07, Wm Stewart <[EMAIL PROTECTED]> wrote: > > > > Good problem solving - however two issues: > > > >* You used V2.2.1 whereas I used V2.1.2. > > Oops... Sloppy reading (or memory). Sorry. > > >* In the middle of my GNUCash i

Re: GnuCash 2.1.2 directions

On 8/31/07, Wm Stewart <[EMAIL PROTECTED]> wrote: > > Good problem solving - however two issues: > >* You used V2.2.1 whereas I used V2.1.2. Oops... Sloppy reading (or memory). Sorry. >* In the middle of my GNUCash installations it stopped while my firewall > asked for permission for "gn

Re: GnuCash 2.1.2 directions

Good problem solving - however two issues: * You used V2.2.1 whereas I used V2.1.2. * In the middle of my GNUCash installations it stopped while my firewall asked for permission for "gnucash-bin.exe" to access the IP. If refused the installation continues but the problem reoccurs, and if

Re: GnuCash 2.1.2 directions

I could not see any communication with 68.142.91.87, or any other external IP during a first setup and running of gnucash-2.2.1. I did a fresh install of Windows XP, installed Wireshark and started to capture packages. Then I ran the gnucash-2.2.1 intallation while capturing. Installation went fi

Re: GnuCash 2.1.2 directions

I will file this as a new item once I find out where. Please note again this is not a duplicate of the known issue you reference -- that issue does not refer to surreptitious external IP connection as a requirement for operation of the application. Christian Stimming wrote: > If you want to disc

Re: GnuCash 2.1.2 directions

If you want to discuss a bugzilla item, please keep this discussion on bugzilla. This is what this is for. Quoting Wm Stewart <[EMAIL PROTECTED]>: > Can someone explain why this bug has been closed, ignored? I honestly > thought after my first notification of surreptitious external IP connectio

Re: GnuCash 2.1.2 directions

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 t

Re: GnuCash 2.1.2 directions

Derek Atkins wrote: > Wm Stewart <[EMAIL PROTECTED]> writes: > >>> I just installed my freshly built gnucash-2.2.1 on Centos-5. While >>> installing gnucash-docs, it tries to contact xml DTD repositories. >>> Is that what is happening on windows? > > I don't think so. This has to do with Gconf

Re: GnuCash 2.1.2 directions

Wm Stewart <[EMAIL PROTECTED]> writes: >> I just installed my freshly built gnucash-2.2.1 on Centos-5. While >> installing gnucash-docs, it tries to contact xml DTD repositories. >> Is that what is happening on windows? I don't think so. This has to do with Gconf/Orbit, not Gnucash or GnuCash-d

Re: GnuCash 2.1.2 directions

Stuart D. Gathman wrote: > On Mon, 27 Aug 2007, Derek Atkins wrote: > >> I'm still wondering WHY it's always trying to contact 68.142.91.87. >> What's so special about that IP Address? > > I just installed my freshly built gnucash-2.2.1 on Centos-5. While > installing gnucash-docs, it tries to

Re: GnuCash 2.1.2 directions

On Mon, 27 Aug 2007, Derek Atkins wrote: > I'm still wondering WHY it's always trying to contact 68.142.91.87. > What's so special about that IP Address? I just installed my freshly built gnucash-2.2.1 on Centos-5. While installing gnucash-docs, it tries to contact xml DTD repositories. Is that

Re: GnuCash 2.1.2 directions

Hi Derek, please let me know if this is excessive cross-posting, I'm new here and not sure what is copied to what. I've updated the bug as follows: http://bugzilla.gnome.org/show_bug.cgi?id=407458#c11 Comments 4, 5, 6, 7, 9 above are not duplicates, they refer to something different, the Window

Re: GnuCash 2.1.2 directions

Quoting Christian Stimming <[EMAIL PROTECTED]>: >> 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 syste

Re: GnuCash 2.1.2 directions

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 Er

Re: GnuCash 2.1.2 directions

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 Wm Stewart wrote: > Perhaps you could test installation of 2.1.

Re: GnuCash 2.1.2 directions

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

Re: GnuCash 2.1.2 directions

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 <[EMAIL PROTECTED]>: > > 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.

Re: GnuCash 2.1.2 directions

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 <[EMAIL

Re: GnuCash 2.1.2 directions

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 <[EMAIL PROTECTED]>: > > Hi, reinstalling did not replicate the error, but starting on a new machine > does. On the new machine, the error we

Re: GnuCash 2.1.2 directions

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 >

Re: GnuCash 2.1.2 directions

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 <[EMAIL PROTECTED]> writes: > The bug occurred again. Two d

Re: GnuCash 2.1.2 directions

The bug occurred again. Two data points: a. It appears to have gone away permanently after I allowed GnuCash to contact an external IP (the GnuCash site?) on start-up. It has not asked to contact that site again, and I have not seen the error again. b. I searched on the text of the bug

Re: GnuCash 2.1.2 directions

Thanks for the report. Has the workaround you metioned fixed the problem permanently? (shutting down gconftool-2 and having it start again when needed) Thanks, Nathan PS: please cc: gnucash-devel On 6/2/07, Wm Stewart <[EMAIL PROTECTED]> wrote: > > > Found a workaround which I documented at the

Re: GnuCash 2.1.2 directions

Good point - Currently we only have the installer on sourceforge. I think we probably need to put a note in that directory to tell people that the installers are on sourceforge Nathan On 6/2/07, Wm Stewart <[EMAIL PROTECTED]> wrote: > > > Thanks much, from the home page I went here and could