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 781859 - hbci-updates.c: 48: Updating user from 5.6.10.0
hbci-updates.c: 48: Updating user from 5.6.10.0
Status: RESOLVED DUPLICATE of bug 781476
Product: GnuCash
Classification: Other
Component: Import - AqBanking
2.6.16
Other Windows
: Normal major
: ---
Assigned To: gnucash-import-maint
gnucash-import-maint
Depends on:
Blocks:
 
 
Reported: 2017-04-27 19:14 UTC by ahtzib+bugzilla.gnome.org
Modified: 2018-06-29 23:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ahtzib+bugzilla.gnome.org 2017-04-27 19:14:13 UTC 
Gnucash crashes when AqBanking is initiated. Since HBCI connections don't run, there is no AqBanking log available. The GnuCash log is:

`
    15:58:04 WARN <gnc.core-utils> Could not kill child process: Zugriff verweigert
    15:58:10 WARN <gnc.backend.sql> [load_account_guid()] Account ref '512d931d38acc15ba6a3b2c37841c4da' not found 

[... above statement repeated multiple times ...]

    15:58:36 WARN <aqhbci> hbci-updates.c: 48: Updating user from 5.6.10.0 
`

after which the application crashes.

I'm using Windows 10 Pro (15063.138) (creator edition)
Comment 1 ahtzib+bugzilla.gnome.org 2017-04-27 19:16:09 UTC 
The updating of a user from 5.6.10.0 never seems to complete because the same message is shown every time I restart GnuCash and run Actions >> Online Actions >> Get Transactions.
Comment 2 John Ralls 2017-04-27 19:21:54 UTC 
Can you get a stack trace (http://wiki.gnucash.org/wiki/Stack_Trace) of the crash?
Comment 3 ahtzib+bugzilla.gnome.org 2017-04-29 06:32:04 UTC 
I installed mingw32 and ran gdb; unfortunately, when I enter the command `bt` to get the backtrace, I get an error:

===========
Starting program: C:/Program Files (x86)/gnucash/bin/gnucash.exe
[New Thread 8572.0x34c0]
[New Thread 8572.0xc18]
[New Thread 8572.0x7c8]
[New Thread 8572.0x2af8]
[New Thread 8572.0x3f98]
[New Thread 8572.0x35cc]
[New Thread 8572.0x3c0c]
[New Thread 8572.0x1f54]
[New Thread 8572.0x16d0]
[New Thread 8572.0x1408]
[New Thread 8572.0x33b0]

Program received signal SIGSEGV, Segmentation fault.
0x0061e44c in ?? ()
(gdb) bt

+ Trace 237408

  • #0 ?? 

Online searches have yielded no information about how to resolve this problem; do you know where I might find out what to do to get a stack trace?

Thanks
Comment 4 John Ralls 2017-04-29 14:26:32 UTC 
You did get a stack trace. The stack has been overwritten with garbage so gdb can't analyze it. That's unfortunate, it makes the problem much harder to track down.
Comment 5 John Ralls 2017-06-25 14:19:08 UTC 
This had already been reported, and I found and fixed the problem yesterday.

*** This bug has been marked as a duplicate of bug 781476 ***
Comment 6 John Ralls 2018-06-29 23:56:20 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=781859. Please update any external references or bookmarks.