GNOME Bugzilla – Bug 564797
2.2.8 won't run on Windows XP: CORBA/COMM_FAILURE
Last modified: 2018-06-29 22:13:58 UTC
I have a Windows XP home SP3 system that has run all previous versions of Gnucash. When trying to load 2.2.8 it makes the screen flash on and off for two minutes then reports an error loading or saving configuration information. The error is given four times as: Adding client to server's list failed. COBRA error IDL:omg/CORBA/COMM_FAILURE:1.0 If you try to proceed the programme makes the screen flash on an off again and hangs with a memory error.
Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 Exactly the same problem as given above, though my screen doesn't flash off and on, I just get a series of command prompts flash up (mostly gconfd-2.exe, once also ntvdm.exe and gconftool-2.exe) and I managed to bog down my CPU so that I could catch the error which is a complaint that the program is too big and not enough mem is available. When the GUI eventually loads, the error i posted at the top is given in the error dialog, same as the other guy.
Oh, I should probably add: the exact error is "program is too big to fit in memory" (on the flashing command prompt EXEs) I'm running Windows Server 2003, Core 2 Duo, 2GB RAM, the previous version of GnuCash runs happily.
OK, just an update now, I found a workaround for the bug: in the libexec folder, replace gconfd-2.exe with the one from 2.2.7, problem solved immediately.
This is my first time installing gnucash. As a first time installer my error message is a little different but related: -------------------------- Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 2: IOR file 'C:\DOCUME~1\Willy\LOCALS~1\Temp\gconfd-Willy/lock/ior' not opened successfully, no gconfd located: No such file or directory) --------------------------- This happened on both XP Pro sp3 at home and XP Home sp3 on the laptop. I uninstalled 2.2.8 and installed 2.2.7 which ran properly. I then uninstalled 2.2.7, reinstalled 2.2.8 and got this message from above: --------------------------- Adding client to server's list failed. COBRA error IDL:omg/CORBA/COMM_FAILURE:1.0 --------------------------- Replacing the gconfd-2.exe file after installation before running the program did the trick for me too.
This occured for me as well XP pro sp2, the flashing windows with "program is too big to fit in memory" eventually followed by gnucash opening with the "Adding client to server's list failed. COBRA error IDL:omg/CORBA/COMM_FAILURE:1.0" error. Taking \Program Files\gnucash\libexec\gconfd-2.exe from 2.2.7 worked for me, but I also found copying the gconfd-2.exe from \Program Files\gnucash\bin\ to \Program Files\gnucash\libexec\ fixed the problem as well.
*** Bug 565049 has been marked as a duplicate of this bug. ***
Same problem here, using WinXP SP3. When I try to run the application a DOS screen pop out and flashes for a couple of minutes, after that the main gnucash window appears and I get the following error Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 I haven't try the work around posted earlier. The same happens when I select any of the menus, like file-->open DOS screen flashing... and the following error Program to big to fit in memory After that the program crashes.
Same here on a Windows XP Prof SP 3: multiple console windows flashing with heading "...gconfd-2.exe" and very short message "program too big to fit into memory"; procmon shows gspawn-win32-helper.exe start a ntvdm (16 bit on 32 bit layer) when loading gconfd-2.exe; looking into the gconfd-2.exe file in the libexec subdir (not the one in the bin subdir!) I found it is lacking the PE-header (not starting with "MZ"), so the OS believes it is a 16 bit app what it apparently is not. BTW, I wonder if there is any 16 bit code there - one hint is that all batch files have the "bat" extension labelling them as 16 bit MSDOS batch files to be run by the 16 bit command.com, as opposed to the "cmd" extension that labels batch files to be run by the true win32 console program cmd.exe. As libexec\gconfd-2.exe seems to be severely broken I wonder if there is *any* NT based system (2k, XP, Vista) running gnucash 2.2.8 properly?
I agree, I can't believe this bug is still in a status of "unconfirmed" I have 2.2.8 running properly if you count the fact I'm using gconfd-2 from 2.2.7 :P
Wondering if they are testing their win builds on win9x or not at all ... Just to add a further detail: same misbehavior with lib\aqbanking\plugins\16\wizards\qt3-wizard.exe: here the PE header is lacking also, seen as 16 bit app, and failing to start: it is invoked by the aqbanking online banking setup wizard, which gives also only a short flashing console window and nothing else; I did not dare to replace this one also with the 2.2.7 counterpart as I am not sure which aqbanking interface is linked - as my 2.2.7 online settings work it seems it is still an aqbanking 2 - I thought the porting to aqbanking 3 had already been done in 2.2.6?!?
Please retry with the updated installer. (In reply to comment #10) > Wondering if they are testing their win builds on win9x or not at all ... Quoting http://wiki.gnucash.org/wiki/Windows#Q:_Is_it_possible_to_compile_GnuCash_on_Windows.3F """Note: Testing indicates that the Windows 9x line (Windows 95, 98, ME) does not run GnuCash.""" > I thought the porting to aqbanking 3 had already been done in 2.2.6?!? Sure, but I will never understand why "added support to compile GnuCash against AqBanking3" indicates that the Windows binary is actually linked against version 3 instead of 2. It does not. If you want to support the migration which is not trivial, please join the -devel or -de mailing list and help us.
(In reply to comment #11) > Please retry with the updated installer. I did, and it works. Checked also all exes for PE headers, and they are now present/correct. This is on XP SP3, but as the origin of the failures has been located and fixed I am pretty sure it should run now on any NT based system, but to be sure someone running Win2K and Vista should confirm this too. > """Note: Testing indicates that the Windows 9x line (Windows 95, 98, ME) does > not run GnuCash.""" If it is clear that the support for DOS-based Win systems has been dropped, the batch files should be renamed to the cmd extension as I lined out earlier. No need to start a 64k limited 16 bit command.com on top of a ntvdm any more ... > If you want to support the migration > which is not trivial, please join the -devel or -de mailing list and help us. Hmm, I see that Shawn Faucher already did most of the work; is there a link to his patched scripts? And as he reported also to be able to build it with aqbanking3 but experienced some misbehavior: is such a build - preferably with the 2.2.8 source - available anywhere?
(In reply to comment #11) > Please retry with the updated installer. > Confirming the reported problem goes away with the new installer for me as well.
Just to confirm that it's also working for me with the new installer (WinXP SP3)
(In reply to comment #12) > (In reply to comment #11) > > Please retry with the updated installer. > > I did, and it works. Checked also all exes for PE headers, and they are now > present/correct. This is on XP SP3, but as the origin of the failures has been > located and fixed I am pretty sure it should run now on any NT based system, > but to be sure someone running Win2K and Vista should confirm this too. Great. Closing this bug as fixed. > > """Note: Testing indicates that the Windows 9x line (Windows 95, 98, ME) does > > not run GnuCash.""" > > If it is clear that the support for DOS-based Win systems has been dropped, the > batch files should be renamed to the cmd extension as I lined out earlier. No > need to start a 64k limited 16 bit command.com on top of a ntvdm any more ... I have created bug 565521 so that we do not forget that (also, feel free to submit an according patch). I will not have access to my Windows box for a few weeks. > > If you want to support the migration > > which is not trivial, please join the -devel or -de mailing list and help us. > > Hmm, I see that Shawn Faucher already did most of the work; is there a link to > his patched scripts? And as he reported also to be able to build it with > aqbanking3 but experienced some misbehavior: is such a build - preferably with > the 2.2.8 source - available anywhere? Those scripts should all be committed to trunk, so you can try to build with install.sh, because AQBANKING3 is yes by default. We could also create a bug to track remaining tasks. Especially, I am interested in a "somewhat smooth" transition from AqBanking2 to AqBanking3.
*** Bug 566511 has been marked as a duplicate of this bug. ***
Phil Longstaff: just for curiosity: why did you change the target milestone to a future version for a bug that has already been fixed with the second 2.2.8 installer? If anything, target milestone was 2.2.8(2)
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=564797. Please update any external references or bookmarks.