GNOME Bugzilla – Bug 486398
Assertion failed: (obj->object_key != NULL); TMP dir permissions
Last modified: 2018-06-29 21:51:49 UTC
Steps to reproduce: 1. just starting Gnucash from the start menu 2. a popup appears whith "Unspecified fatale error encountered, aborting" 3. a second popup appears, titled "Microsoft visual C++ Runtime Library". It says "Runtime error! Program C:\......\Gnucash\bin\gnucash-bin.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." Stack trace: Other information: Gnucash worked fine for two days, I installed/unistalled nothing new before it started mulfunctioning.....
... tried to unistall and install it again, but aleays the same error. .. sorry, but I do not know how to report a stack trace...
A few questions: Does gnucash work when you * start it without a file, i.e. append " --nofile" to the last line (start gnucash-bin) of bin\gnucash.bat * start it without your preference settings, i.e. make sure no gconfd-2.exe process is running, move ~\.gconf and ~\.gconfd to a backup location, where ~ is C:\Documents and Settings\$user * start it without your reports, i.e. move ~\.gnucash to a backup location Is there anything valuable in ~\Local Settings\Temp\gnucash.trace.ABCDEF? You might also want to take a look at http://wiki.gnucash.org/wiki/Windows for additional information. Maybe you find a step-by-step guide to reproduce this bug, starting from an empty file. Or you can provide a minimal test file.
Hi, unfortunately none of the 3 suggestion mentioned above worked. Here is the content of "gnucash.trace.RGGH0T" * OTHER <> file corba-object.c: line 76 (ORBit_register_objref): assertion failed: (obj->object_key != NULL) I managed to get it working using the workaround described in http://wiki.gnucash.org/wiki/Windows#Windows_XP_Home_Edition_Problems I changed the TMP and TEMP environment variables and it started working!!!!!
*** Bug 490255 has been marked as a duplicate of this bug. ***
Is this bug#457100? (OTOH that one is too long to be understandable anymore.) The solution in the wiki page was given as follows: I was able to resolve this problem by creating a new temporary directory (e.g. c:\temp) and setting environmental variables TEMP and TMP to point to this new directory. There is something odd about the permissions on the temporary directory created by orbit.
*** Bug 490665 has been marked as a duplicate of this bug. ***
This bug describes the TMP and TEMP permission issue and the ior file in the TEMP directory: * bug 449153 * bug 457100 comment 33, bug 457100 comment 52, bug 457100 comment 62, bug 457100 comment 75 * We've got a permission problem in gnucash ourselves, bug 466512, which we need to fix in gnucash, but this is unrelated to the TEMP and TMP directories.
*** Bug 457100 has been marked as a duplicate of this bug. ***
*** Bug 502235 has been marked as a duplicate of this bug. ***
Christian, may you please summarize once again, now GnuCash 2.2.2 is out? :-D
(In reply to comment #10) I had same problems with v2.2.8. None of above mentioned solutions worked for me. ...but finally I have found a solution which works for me: Deactivation of SW-firewall. Maybe doing this could help others too...
*** Bug 577894 has been marked as a duplicate of this bug. ***
aargh pls fix this this bug makes me cry i worked hard to convince my dad to try gnucash on his xp and this really disappointed all of us.
Re comment#11: This is bug#510720. The solution in the wiki page was given as follows: I was able to resolve this problem by creating a new temporary directory (e.g. c:\temp) and setting environmental variables TEMP and TMP to point to this new directory. There is something odd about the permissions on the temporary directory created by orbit. Do people still see an assertion failed (obj->object_key != NULL) with the 2.3.8 version?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Here, the solution was to allow all local loopback connections in the firewall. As this often is not acceptable/desirable under Windows, could you please add information to the installation readme which binaries need loopback allowance. Thanks.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=486398. Please update any external references or bookmarks.