After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 506499 - Win32: Crash after online banking transfer
Win32: Crash after online banking transfer
Status: VERIFIED FIXED
Product: GnuCash
Classification: Other
Component: General
2.2.x
Other Windows
: Normal critical
: ---
Assigned To: Christian Stimming
Christian Stimming
Depends on:
Blocks: backport
 
 
Reported: 2007-12-30 23:20 UTC by Patrick Schoenbach
Modified: 2018-06-29 21:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Patrick Schoenbach 2007-12-30 23:20:43 UTC
After a successful online debit on my Postbank account, GnuCash always crashes. The transfer is being made, however, the transaction inside GnuCash gets lost. Since I am experiencing this on Windows, I unfortunately cannot provide a stack trace.
Comment 1 Timm Reinstorf 2008-01-11 18:27:06 UTC
Same here, on windows as well. Occurs in version 2.2.1 and 2.2.3.

This gets written to the trace file:
------------------------
*   WARN <qof.engine> [guid_init()] only got 1840 bytes.
The identifiers might not be very random.
*   WARN <Gdk> gdkselection-win32.c:1068: OpenClipboard failed: Ungültiges Fensterhandle
*   WARN <Gdk> gdkselection-win32.c:1068: OpenClipboard failed: Ungültiges Fensterhandle
*   WARN <Gdk> gdkselection-win32.c:1068: OpenClipboard failed: Ungültiges Fensterhandle
*   WARN <gnc.import.hbci> gnc_hbci_debug_outboxjob: Job status: error
-----------------------

"Ungültiges Fensterhandle" translates to "invalid window handle"
Comment 2 Derek Atkins 2008-05-01 21:01:35 UTC
I think I fixed this in r17146.  Awaiting backport to 2.2
Can you test this patch and see if it fixes it for you?
Thanks to Jannick Asmus for the backtrace
Comment 3 Timm Reinstorf 2008-05-03 07:25:35 UTC
Thanks for the fix! I tried to test this on windows, but unfortunately could not get gnucash to work.

I compiled r17148 using install.sh (took a very looong time on msys).

Gnucash crashes during startup with no further messages. The last status message in the startup splash screen says "gnucash/business-gnome".

The trace file contains:
*   WARN <qof.engine> [guid_init()] only got 1756 bytes.
The identifiers might not be very random.
*   CRIT <gnc.gui> [gnc_gnome_locate_data_file()] Could not locate file ui/gnc-plugin-csv-ui.xml


The file "ui/gnc-plugin-csv-ui.xml" is located under ${INSTALLDIR}\share\gnucash. I tried to add this directory to all env vars set in gnucash.bat, but with no success. The gnucash console (I changed the exetype of gnucash-bin.exe to console) also does not show any errors (only a message stating that this is a dev-version, and the next stable will be 2.4).

Any ideas what I could try or where to find an error message? Could the gnc-plugin-csv-ui.xml be the problem?
Comment 4 Andreas Köhler 2008-05-05 22:06:52 UTC
I know this sounds absurd, but may you uninstall gnucash before?  I think it is picking up the wrong installation from the registry which lacks the file mentioned.
Honestly, I guess cstim and I will have to fix that someday :)
Comment 5 Timm Reinstorf 2008-05-12 14:51:08 UTC
Yes, uninstalling Gnucash 2.2.5 before starting the newly build Gnucash helped to get rid of the "Could not locate file ui/gnc-plugin-csv-ui.xml" message.

Nevertheless, Gnucash does not start. It shows the splash screen (last message "gnucash/business-gnome"), and then dies without any error messages.

Sorry, I think I will wait for Gnucash 2.2.6 and test with the binary version (hoping that the fix will be included in 2.2.6).
Comment 6 Andreas Köhler 2008-05-12 15:20:00 UTC
Please try to provide us with a stacktrace as described at http://wiki.gnucash.org/wiki/Windows#Debugging_with_gdb.  Maybe it contains some additional information for us.
Comment 7 Timm Reinstorf 2008-06-10 16:10:42 UTC
I tried to get a stacktrace by running gnucash from gdb, but "bt" returned nothing. I guess that gnucash exists "cleanly" during startup and does not crash (regarding comment #3, not the topic of this report) and therefore no stack trace is produced? Probably I messed up something with my environment or build. The problem that I could not start a self-build gnucash is probably totally unrelated to the bug discussed here.

So, please excuse that I can not confirm that the patch fixes the original bug. I will come back and report, after gnucash 2.2.6 is out.
Comment 8 Andreas Köhler 2008-07-20 22:41:06 UTC
> I think I fixed this in r17146.  Awaiting backport to 2.2

Applied to branches/2.2 as r17166 by cstim for inclusion in GnuCash 2.2.6.
Thanks.
Comment 9 John Ralls 2018-06-29 21:57:57 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=506499. Please update any external references or bookmarks.