Re: [GNC-dev] Mouse usage in Gnucash
Hi Frank, Sorry I am referrring to the glossary currently in the guide. Ok found the 1.79.2/html/glossary.xsl but it is beyond my current understanding of xsl processing to modify it. I am slowly getting the idea but don't want to invest the time at tis point to get up to speed. I'll add the appropriate references to the gnome hig in the gnc-docbookx.dtd as you suggested. David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] segmentation fault / gnucash crashing upon using online banking actions
Thanks for helping me out with this. How could I oversee this? I removed all those much older repository packages which I had installed some time late at night tired from failing. Compiling succeeded with de_DE and we're back in book keeping! Online actions working fine. Trying to transfer a donation via Gnucash SEPA transfer to Geert Jaansens account failed somehow. I will use the Browser for now and look into that issue tommorrow. Best wishes to all of you have a great day Alex PS. tax export still crashing giving segmentation fault error. On Tue, 15 Oct 2019 06:08:29 -0400 "Derek Atkins" wrote: > Hi, > > It looks like you may have a system-installed libgwenhywfar? It's > finding (and using) one from /usr/lib/x86_64-linux-gnu/ ?? > > -derek > > > On Tue, October 15, 2019 6:00 am, Alex wrote: > > First of all, I forgot to say I'm on Linux Debian, sorry @Martin > > for not mentioning! > > > > Dear Christian, > > > > I'm not sure if the "--enable-debug" flag changed the output of > > the first lines of the gdb backtrace in any way, please see > > below, to me they seem just the same... > > > > Here's what I dit: > > > > recompiled gwenhywfar: > > I did not git pull, so we are as of Oct 14th. > > $ export LANG="C" > > $ ./configure --with-guis="gtk3" --enable-debug > > > > also recompiled aqb and gnucash. > > > > Then ran: > > $ gdb gnucash > > (gdb) run --debug --extra > > Starting program: /usr/local/bin/gnucash --debug --extra > > [Thread debugging using libthread_db enabled] > > Using host libthread_db library > > "/lib/x86_64-linux-gnu/libthread_db.so.1". [ … here's some > > various gnucash startup debugging outputs … ] > > > > Gnucash is open. Empty file. I enter the aqbanking wizard > > straight away, "edit" the only existing user, "get certificate", > > OK, "Get Bank Info", Crash. > > > > Here's the first lines of the backtrace: > > > > Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault. > > 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () > >from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > > (gdb) bt full > > #0 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () > > at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > > #1 0x7fffba4325a3 in GWEN_ConfigMgrDir_AddGroupFileName () > > at > > /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so > > #2 0x7fffba43318e in GWEN_ConfigMgrDir_DeleteGroup () at > > /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so > > #3 0x7fffd6539e8c in AB_Banking_ReadConfigGroup > > (ab=0x57dda620, groupName=groupName@entry=0x7fffd66b8393 > > "users", uniqueId=uniqueId@entry=1, doLock=doLock@entry=1, > > doUnlock=doUnlock@entry=0, pDb=pDb@entry=0x7fff70c8) at > > banking_cfg.c:413 rv = > > idBuf = > > "\230'\aXUU\000\000\002\000\000\000\000\000\000\000\000(\aXUU", > > '\000' , > > "Q\303\312\352\377\177\000\000\000\000\000\000\000\000\000\000\020%\217UUU\000\000 > > \217\225UUU\000\000\300m\377\377\377\177\000\000\377\377\377\377\377\377\377\377\357\252\312\352\377\177\000\000\000\000\000\000\000\000\000\000\030\275\024\367\377\177\000\000\377\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000@\257\225UUU\000\000pn\377\377\377\177\000\000c\276\024\367\377\177\000\000pn\377\377\377\177\000\000\277\276\024\367\377\177\000\000\v\272\336\352\377\177\000\000\200\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\000"... > > __PRETTY_FUNCTION__ = "AB_Banking_ReadConfigGroup" > > #4 0x7fffd653d9a1 in AB_Banking_Read_UserConfig > > (ab=, uid=uid@entry=1, doLock=doLock@entry=1, > > doUnlock=doUnlock@entry=0, pDb=pDb@entry=0x7fff70c8) > > at banking_user.c:20 > > rv = > > #5 0x7fffd6552110 in AB_Provider_ReadUser > > (pro=pro@entry=0x57b0a2f0, uid=uid@entry=1, > > doLock=doLock@entry=1, doUnlock=doUnlock@entry=0, > > user=user@entry=0x57b0b900) at provider_user.c:24 > > rv = > > db = 0x0 > > uidInDb = > > #6 0x7fffd6552b77 in AB_Provider_BeginExclUseUser > > (pro=0x57b0a2f0, u=0x57b0b900) at provider_user.c:226 > > rv = > > uid = 1 > > [ … and so on … ] > > > > Please let me know if I can do anything else. > > > > Kindly > > Alex > > > > On Mon, 14 Oct 2019 21:51:41 +0200 > > Christian Stimming wrote: > > > >> Dear Alex, > >> > >> we're getting closer... the libaqbanking lines already have full > >> debug info, but only the libgwenhywfar do not have it. Can you > >> compile again gwenhywfar, this time with --enable-debug, so that > >> the first few lines from the backtrace (only those are important) > >> contain some more information such as the function arguments? > >> This would be a big help. Thanks! > >> > >> Regards, > >> Christian > >> > >> Am Montag, 14. Oktober 2019, 18:15:00 CEST schrieb Alex: > >> > Here is a backtrace of Gnucash when crashing upon clicking on > >> > "Get Bank Info" in the aqbanking wizard. Let me know if I
Re: [GNC-dev] segmentation fault / gnucash crashing upon using online banking actions
As derek already said: you are using a system-installed gwenhywfar. You need to check at aqbanking configure time that it really chose the correct libgwenhywfar, and gnucash subsequently too. Thanks! Christian > Am 15.10.2019 um 12:00 schrieb Alex : > > First of all, I forgot to say I'm on Linux Debian, sorry @Martin for not > mentioning! > > Dear Christian, > > I'm not sure if the "--enable-debug" flag changed the output of the first > lines of the gdb backtrace in any way, please see below, to me they seem just > the same... > > Here's what I dit: > > recompiled gwenhywfar: > I did not git pull, so we are as of Oct 14th. > $ export LANG="C" > $ ./configure --with-guis="gtk3" --enable-debug > > also recompiled aqb and gnucash. > > Then ran: > $ gdb gnucash > (gdb) run --debug --extra > Starting program: /usr/local/bin/gnucash --debug --extra > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [ … here's some various gnucash startup debugging outputs … ] > > Gnucash is open. Empty file. I enter the aqbanking wizard straight away, > "edit" the only existing user, "get certificate", OK, "Get Bank Info", Crash. > > Here's the first lines of the backtrace: > > Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault. > 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () > from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > (gdb) bt full > #0 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () >at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > #1 0x7fffba4325a3 in GWEN_ConfigMgrDir_AddGroupFileName () >at /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so > #2 0x7fffba43318e in GWEN_ConfigMgrDir_DeleteGroup () >at /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so > #3 0x7fffd6539e8c in AB_Banking_ReadConfigGroup (ab=0x57dda620, > groupName=groupName@entry=0x7fffd66b8393 "users", uniqueId=uniqueId@entry=1, > doLock=doLock@entry=1, doUnlock=doUnlock@entry=0, > pDb=pDb@entry=0x7fff70c8) at banking_cfg.c:413 >rv = >idBuf = > "\230'\aXUU\000\000\002\000\000\000\000\000\000\000\000(\aXUU", '\000' > , > "Q\303\312\352\377\177\000\000\000\000\000\000\000\000\000\000\020%\217UUU\000\000 > > \217\225UUU\000\000\300m\377\377\377\177\000\000\377\377\377\377\377\377\377\377\357\252\312\352\377\177\000\000\000\000\000\000\000\000\000\000\030\275\024\367\377\177\000\000\377\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000@\257\225UUU\000\000pn\377\377\377\177\000\000c\276\024\367\377\177\000\000pn\377\377\377\177\000\000\277\276\024\367\377\177\000\000\v\272\336\352\377\177\000\000\200\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\000"... >__PRETTY_FUNCTION__ = "AB_Banking_ReadConfigGroup" > #4 0x7fffd653d9a1 in AB_Banking_Read_UserConfig (ab=, > uid=uid@entry=1, doLock=doLock@entry=1, doUnlock=doUnlock@entry=0, > pDb=pDb@entry=0x7fff70c8) >at banking_user.c:20 >rv = > #5 0x7fffd6552110 in AB_Provider_ReadUser (pro=pro@entry=0x57b0a2f0, > uid=uid@entry=1, doLock=doLock@entry=1, doUnlock=doUnlock@entry=0, > user=user@entry=0x57b0b900) >at provider_user.c:24 >rv = >db = 0x0 >uidInDb = > #6 0x7fffd6552b77 in AB_Provider_BeginExclUseUser (pro=0x57b0a2f0, > u=0x57b0b900) at provider_user.c:226 >rv = >uid = 1 > [ … and so on … ] > > Please let me know if I can do anything else. > > Kindly > Alex > > On Mon, 14 Oct 2019 21:51:41 +0200 > Christian Stimming wrote: > >> Dear Alex, >> >> we're getting closer... the libaqbanking lines already have full >> debug info, but only the libgwenhywfar do not have it. Can you >> compile again gwenhywfar, this time with --enable-debug, so that >> the first few lines from the backtrace (only those are important) >> contain some more information such as the function arguments? This >> would be a big help. Thanks! >> >> Regards, >> Christian >> >> Am Montag, 14. Oktober 2019, 18:15:00 CEST schrieb Alex: >>> Here is a backtrace of Gnucash when crashing upon clicking on >>> "Get Bank Info" in the aqbanking wizard. Let me know if I can do >>> anything else. >>> >>> -- GDB BACKTRACE START --- >>> >>> Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault. >>> 0x7fffd6075989 in GWEN_Text_EscapeToBuffer () >>> from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 >>> (gdb) bt full >>> #0 0x7fffd6075989 in GWEN_Text_EscapeToBuffer () >>>at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 >>> #1 0x7fffbe22d5a3 in GWEN_ConfigMgrDir_AddGroupFileName () >>>at >>> /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so >>> #2 0x7fffbe22e18e in GWEN_ConfigMgrDir_DeleteGroup () at >>> /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so >>> #3 0x7fffd632be8c in AB_Banking_ReadConfigGroup >>>
Re: [GNC-dev] segmentation fault / gnucash crashing upon using online banking actions
Hi, It looks like you may have a system-installed libgwenhywfar? It's finding (and using) one from /usr/lib/x86_64-linux-gnu/ ?? -derek On Tue, October 15, 2019 6:00 am, Alex wrote: > First of all, I forgot to say I'm on Linux Debian, sorry @Martin for not > mentioning! > > Dear Christian, > > I'm not sure if the "--enable-debug" flag changed the output of the first > lines of the gdb backtrace in any way, please see below, to me they seem > just the same... > > Here's what I dit: > > recompiled gwenhywfar: > I did not git pull, so we are as of Oct 14th. > $ export LANG="C" > $ ./configure --with-guis="gtk3" --enable-debug > > also recompiled aqb and gnucash. > > Then ran: > $ gdb gnucash > (gdb) run --debug --extra > Starting program: /usr/local/bin/gnucash --debug --extra > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [ … here's some various gnucash startup debugging outputs … ] > > Gnucash is open. Empty file. I enter the aqbanking wizard straight away, > "edit" the only existing user, "get certificate", OK, "Get Bank Info", > Crash. > > Here's the first lines of the backtrace: > > Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault. > 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () >from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > (gdb) bt full > #0 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () > at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > #1 0x7fffba4325a3 in GWEN_ConfigMgrDir_AddGroupFileName () > at /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so > #2 0x7fffba43318e in GWEN_ConfigMgrDir_DeleteGroup () > at /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so > #3 0x7fffd6539e8c in AB_Banking_ReadConfigGroup (ab=0x57dda620, > groupName=groupName@entry=0x7fffd66b8393 "users", > uniqueId=uniqueId@entry=1, doLock=doLock@entry=1, > doUnlock=doUnlock@entry=0, pDb=pDb@entry=0x7fff70c8) at > banking_cfg.c:413 > rv = > idBuf = > "\230'\aXUU\000\000\002\000\000\000\000\000\000\000\000(\aXUU", > '\000' , > "Q\303\312\352\377\177\000\000\000\000\000\000\000\000\000\000\020%\217UUU\000\000 > \217\225UUU\000\000\300m\377\377\377\177\000\000\377\377\377\377\377\377\377\377\357\252\312\352\377\177\000\000\000\000\000\000\000\000\000\000\030\275\024\367\377\177\000\000\377\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000@\257\225UUU\000\000pn\377\377\377\177\000\000c\276\024\367\377\177\000\000pn\377\377\377\177\000\000\277\276\024\367\377\177\000\000\v\272\336\352\377\177\000\000\200\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\000"... > __PRETTY_FUNCTION__ = "AB_Banking_ReadConfigGroup" > #4 0x7fffd653d9a1 in AB_Banking_Read_UserConfig (ab=, > uid=uid@entry=1, doLock=doLock@entry=1, doUnlock=doUnlock@entry=0, > pDb=pDb@entry=0x7fff70c8) > at banking_user.c:20 > rv = > #5 0x7fffd6552110 in AB_Provider_ReadUser > (pro=pro@entry=0x57b0a2f0, uid=uid@entry=1, doLock=doLock@entry=1, > doUnlock=doUnlock@entry=0, user=user@entry=0x57b0b900) > at provider_user.c:24 > rv = > db = 0x0 > uidInDb = > #6 0x7fffd6552b77 in AB_Provider_BeginExclUseUser > (pro=0x57b0a2f0, u=0x57b0b900) at provider_user.c:226 > rv = > uid = 1 > [ … and so on … ] > > Please let me know if I can do anything else. > > Kindly > Alex > > On Mon, 14 Oct 2019 21:51:41 +0200 > Christian Stimming wrote: > >> Dear Alex, >> >> we're getting closer... the libaqbanking lines already have full >> debug info, but only the libgwenhywfar do not have it. Can you >> compile again gwenhywfar, this time with --enable-debug, so that >> the first few lines from the backtrace (only those are important) >> contain some more information such as the function arguments? This >> would be a big help. Thanks! >> >> Regards, >> Christian >> >> Am Montag, 14. Oktober 2019, 18:15:00 CEST schrieb Alex: >> > Here is a backtrace of Gnucash when crashing upon clicking on >> > "Get Bank Info" in the aqbanking wizard. Let me know if I can do >> > anything else. >> > >> > -- GDB BACKTRACE START --- >> > >> > Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault. >> > 0x7fffd6075989 in GWEN_Text_EscapeToBuffer () >> >from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 >> > (gdb) bt full >> > #0 0x7fffd6075989 in GWEN_Text_EscapeToBuffer () >> > at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 >> > #1 0x7fffbe22d5a3 in GWEN_ConfigMgrDir_AddGroupFileName () >> > at >> > /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so >> > #2 0x7fffbe22e18e in GWEN_ConfigMgrDir_DeleteGroup () at >> > /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so >> > #3 0x7fffd632be8c in AB_Banking_ReadConfigGroup >> > (ab=0x582f8820, groupName=groupName@entry=0x7fffd64aa393 >> > "users",
Re: [GNC-dev] segmentation fault / gnucash crashing upon using online banking actions
Additionally, here's the last lines of the /tmp/gnucash.trace file: * 11:48:56 INFO job_new.c: 339: Single message job │ * 11:48:56 INFO jobgetbankinfo.c: 71: JobGetBankInfo created │ * 11:48:56 INFO outbox.c: 1182: CBox for customer "XXX" not found │ * 11:48:56 MESSG outbox.c: 1203: Creating CBox for customer "XXX" │ * 11:48:56 INFO job.c: 616: Changing status of job "JobGetBankInfo" from "unknown" (0) to "todo" (1) │ * 11:48:56 INFO outbox.c: 1090: Locking customer "1" │ * 11:48:56 INFO provider_user.c: 224: Locking customer "1" On Tue, 15 Oct 2019 12:00:33 +0200 Alex wrote: > First of all, I forgot to say I'm on Linux Debian, sorry @Martin > for not mentioning! > > Dear Christian, > > I'm not sure if the "--enable-debug" flag changed the output of the > first lines of the gdb backtrace in any way, please see below, to > me they seem just the same... > > Here's what I dit: > > recompiled gwenhywfar: > I did not git pull, so we are as of Oct 14th. > $ export LANG="C" > $ ./configure --with-guis="gtk3" --enable-debug > > also recompiled aqb and gnucash. > > Then ran: > $ gdb gnucash > (gdb) run --debug --extra > Starting program: /usr/local/bin/gnucash --debug --extra > [Thread debugging using libthread_db enabled] > Using host libthread_db library > "/lib/x86_64-linux-gnu/libthread_db.so.1". [ … here's some various > gnucash startup debugging outputs … ] > > Gnucash is open. Empty file. I enter the aqbanking wizard straight > away, "edit" the only existing user, "get certificate", OK, "Get > Bank Info", Crash. > > Here's the first lines of the backtrace: > > Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault. > 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () >from /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > (gdb) bt full > #0 0x7fffd6283989 in GWEN_Text_EscapeToBuffer () > at /usr/lib/x86_64-linux-gnu/libgwenhywfar.so.60 > #1 0x7fffba4325a3 in GWEN_ConfigMgrDir_AddGroupFileName () > at > /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so #2 > 0x7fffba43318e in GWEN_ConfigMgrDir_DeleteGroup () at > /usr/lib/x86_64-linux-gnu/gwenhywfar/plugins/60/configmgr/dir.so #3 > 0x7fffd6539e8c in AB_Banking_ReadConfigGroup > (ab=0x57dda620, groupName=groupName@entry=0x7fffd66b8393 > "users", uniqueId=uniqueId@entry=1, doLock=doLock@entry=1, > doUnlock=doUnlock@entry=0, pDb=pDb@entry=0x7fff70c8) at > banking_cfg.c:413 rv = idBuf = > "\230'\aXUU\000\000\002\000\000\000\000\000\000\000\000(\aXUU", > '\000' , > "Q\303\312\352\377\177\000\000\000\000\000\000\000\000\000\000\020%\217UUU\000\000 > \217\225UUU\000\000\300m\377\377\377\177\000\000\377\377\377\377\377\377\377\377\357\252\312\352\377\177\000\000\000\000\000\000\000\000\000\000\030\275\024\367\377\177\000\000\377\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000@\257\225UUU\000\000pn\377\377\377\177\000\000c\276\024\367\377\177\000\000pn\377\377\377\177\000\000\277\276\024\367\377\177\000\000\v\272\336\352\377\177\000\000\200\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\000"... > __PRETTY_FUNCTION__ = "AB_Banking_ReadConfigGroup" #4 > 0x7fffd653d9a1 in AB_Banking_Read_UserConfig (ab= out>, uid=uid@entry=1, doLock=doLock@entry=1, > out>doUnlock=doUnlock@entry=0, pDb=pDb@entry=0x7fff70c8) at > out>banking_user.c:20 rv = #5 0x7fffd6552110 > out>in AB_Provider_ReadUser (pro=pro@entry=0x57b0a2f0, > out>uid=uid@entry=1, doLock=doLock@entry=1, > out>doUnlock=doUnlock@entry=0, user=user@entry=0x57b0b900) at > out>provider_user.c:24 rv = db = 0x0 uidInDb = > out> #6 0x7fffd6552b77 in > out>AB_Provider_BeginExclUseUser (pro=0x57b0a2f0, > out>u=0x57b0b900) at provider_user.c:226 > rv = > uid = 1 > [ … and so on … ] > > Please let me know if I can do anything else. > > Kindly > Alex > > On Mon, 14 Oct 2019 21:51:41 +0200 > Christian Stimming wrote: > > > Dear Alex, > > > > we're getting closer... the libaqbanking lines already have full > > debug info, but only the libgwenhywfar do not have it. Can you > > compile again gwenhywfar, this time with --enable-debug, so that > > the first few lines from the backtrace (only those are important) > > contain some more information such as the function arguments? This > > would be a big help. Thanks! > > > > Regards, > > Christian > > > > Am Montag, 14. Oktober 2019, 18:15:00 CEST schrieb Alex: > > > Here is a backtrace of Gnucash
