Transaction Report Repeatedly Crashes GNUCash 2.6.1

Sat Mar 22 09:08:10 EDT 2014

All,

Ok, retract claws please....  I googled a bit and discovered that Debian
systems apparently don't use rpms, but something called .deb files.  (I
have never used Debian).  So I found:
https://packages.debian.org/search?keywords=gnucash  and this webpage only
offers version 2.6.1 -- what you are using.  No 2.6.2.  With deb files it
looks like you are stuck at 2.6.1.

But, rpm files for 2.6.2 are available (
http://rpm.pbone.net/index.php3?stat=3&search=gnucash&srodzaj=3).  And
there is a method out there for converting rpm files to deb files (
http://www.debianadmin.com/install-rpm-files-in-debian-and-ubuntu.html).
So maybe you would consider installing "alien" via apt-get, grabbing the
rpm for 2.6.2, converting and installing it, and giving things another go.
If you can install 2.6.2 in an alternate location so you don't mash 2.6.1,
that would probably be a good idea.

Jeff

On Fri, Mar 21, 2014 at 6:10 PM, Mark Phillips
<mark at phillipsmarketing.biz>wrote:

> David and Jeff,
>
> David, perhaps you didn't read the exchange between Jeff and me before
> your post. Jeff also suggested that I upgrade, and I pointed out to him
> that was not really an option because 2.6.2 is not available for Debian
> testing.
>
> If you had said something like the change log for 2.6.2 indicates that the
> errors you are seeing are fixed in that upgrade, that would have been a
> different story. But to insist that the only way to get any help would be
> to make significant changes to my OS without any reason, especially after
> Jeff and I had already gone down that path and I had explained why that
> solution was not a good idea, was not helpful.
>
> Jeff, there are many good and tested reasons why apps go from Debian
> unstable to testing to stable, and one should not have to change the
> operating system to get help on a point release that was released less than
> three months ago. Changing a Debian system from testing to unstable or a
> mixed testing and unstable configuration is opening pandora's box for all
> sorts of conflicts with all the other software on my computer.
>
> Again, I would love to have a discussion with someone who can interpret
> the error messages I included in my first email and help me diagnose this
> problem.
>
> Mark
>
>
> On Fri, Mar 21, 2014 at 2:29 PM, David T. <sunfish62 at yahoo.com> wrote:
>
>> Mark,
>>
>> I'm sorry you interpreted my reply as full of hubris. I am neither a
>> programmer nor a user of Linux, but merely another user of GnuCash.
>>
>> If you read my message, I made no assertion about your operating system.
>> I merely suggested that you might upgrade to the latest stable release to
>> see whether that fixed your problem. I was under the impression that there
>> are repositories that offer 2.6.2 from which you could update, but
>> apparently I was mistaken.
>>
>> Good luck on fixing the problem. I hope someone else will be able to help
>> you with it.
>>
>> David
>>
>>   ------------------------------
>>  *From:* Mark Phillips <mark at phillipsmarketing.biz>
>> *To:* David T. <sunfish62 at yahoo.com>
>> *Cc:* Jeff Earickson <jaearick at colby.edu>; Gnucash Users <
>> gnucash-user at gnucash.org>
>> *Sent:* Friday, March 21, 2014 12:24 PM
>>
>> *Subject:* Re: Transaction Report Repeatedly Crashes GNUCash 2.6.1
>>
>> David,
>>
>> I find it the hight of hubris to recommend changing one's operating
>> system in order to migrate to a point release that is not even 3 months old
>> in an application. If you know of a bug that is fixed in 2.6.2 that
>> addresses the errors I have reported, then I will consider upgrading or
>> wait for the Debian maintainer to migrate 2.6.2 to testing. However, by
>> your own admission, you have no idea what is causing the problem, so
>> stridently saying I have no other choice to get help unless I mangle my
>> operating system and upgrade to 2.6.2 is not very helpful or friendly. If,
>> as you say, I still have the problem after upgrading, will you recommend I
>> change my operating system to Windows 8? Maybe try Fedora and hope for the
>> best?
>>
>> Let me rephrase my request for help. Is there someone on the list who
>> understands the debugging information I provided for the error I am
>> experiencing, and would he or she be able to help me diagnose what is going
>> on so I can fix the problem?
>>
>> Thanks,
>>
>> Mark
>>
>>
>> On Fri, Mar 21, 2014 at 11:51 AM, David T. <sunfish62 at yahoo.com> wrote:
>>
>>  Mark,
>>
>>  GnuCash 2.6.2 is more stable than 2.6.1, and fixes a number of issues,
>> and perhaps yours. The fact that Debian is not up-to-date is beside the
>> point. Since you're having troubles with 2.6.1, you'd well advised to seek
>> out 2.6.2 through whatever channels you can. Then, if the problem persists,
>> the developers can help track down the source.
>>
>> David
>>
>>   ------------------------------
>>  *From:* Mark Phillips <mark at phillipsmarketing.biz>
>> *To:* Jeff Earickson <jaearick at colby.edu>
>> *Cc:* Gnucash Users <gnucash-user at gnucash.org>
>> *Sent:* Friday, March 21, 2014 9:41 AM
>> *Subject:* Re: Transaction Report Repeatedly Crashes GNUCash 2.6.1
>>
>> Jeff,
>>
>> I usually just run Debian testing and rely on apt to update packages as
>> needed. 2.6.2 is still in unstable, so I am reluctant to run a mixed
>> testing/unstable system. Is there another way to find out what is missing
>> or going wrong with my current installation?
>>
>> Mark
>>
>>
>> On Fri, Mar 21, 2014 at 9:36 AM, Jeff Earickson <jaearick at colby.edu>
>> wrote:
>>
>> > Mark,
>> >
>> > Can you try it with gnucash 2.6.2 and see if you get the same crash?
>> >
>> > Jeff
>> >
>> > On Fri, Mar 21, 2014 at 11:41 AM, Mark Phillips <
>> > mark at phillipsmarketing.biz> wrote:
>> >
>> >> I have been using GC for several years and have not had any issues. I
>> am
>> >> running GC 2.6.1 on Linux version 3.1.0-1-amd64 (Debian 3.1.8-2).
>> However,
>> >> recently when I try to run a transaction report, GC crashes with a
>> brief
>> >> message that says there was an error running the report (it flashes on
>> the
>> >> screen, the the program goes away). I looked in the gnucash.trace file
>> and
>> >> found -
>> >>
>> >> root at orca:/tmp# cat gnucash.trace
>> >> * 08:33:18 WARN <gnc.backend.dbi> [gnc_module_init_backend_dbi()] No
>> DBD
>> >> drivers found
>> >> * 08:33:26 WARN <gnc.python> Unable to initialize Python module
>> (unable to
>> >> open /usr/share/gnucash/python/init.py)
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:33:58 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:35:18 CRIT <gnc.app-utils> gnc_option_set_selectable: assertion
>> >> 'option->odb->set_selectable != NULL' failed
>> >> * 08:36:08 WARN <gnc.report.core> Failure running report: ERROR: In
>> >> procedure apply-smob/1:
>> >> ERROR: Wrong number of arguments to #<procedure display-error (_ _ _ _
>> _
>> >> _)>
>> >> In unknown file:
>> >> ?: 19 [apply-smob/1 #<catch-closure 3472920>]
>> >> ?: 18 [call-with-input-string "(gnc:report-run 1)" ...]
>> >> In ice-9/boot-9.scm:
>> >> 2320: 17 [save-module-excursion #<procedure 4c2a150 at
>> >> ice-9/eval-string.scm:65:9 ()>]
>> >> In ice-9/eval-string.scm:
>> >> 44: 16 [read-and-eval #<input: string 5198680> #:lang ...]
>> >> 37: 15 [lp (gnc:report-run 1)]
>> >> In report.scm:
>> >> 766: 14 [gnc:report-run 1]
>> >> In ice-9/boot-9.scm:
>> >> 157: 13 [catch ignore #<procedure 3473d80 at gnucash/main.scm:112:4 ()>
>> >> ...]
>> >> In unknown file:
>> >> ?: 12 [lazy-catch #t #<procedure 3473d20 at gnucash/main.scm:114:18 ()>
>> >> ...]
>> >> In ice-9/boot-9.scm:
>> >> 171: 11 [with-throw-handler #t #<catch-closure 34725e0> #<catch-closure
>> >> 34725c0>]
>> >> In unknown file:
>> >> ?: 10 [apply-smob/1 #<catch-closure 34725e0>]
>> >> In report.scm:
>> >> 770: 9 [#<procedure 3473db0 at report.scm:767:5 ()>]
>> >> 749: 8 [gnc:report-render-html # #t]
>> >> In html-document.scm:
>> >> 196: 7 [gnc:html-document-render # #t]
>> >> In ice-9/boot-9.scm:
>> >> 102: 6 [#<procedure 54ddb80 at ice-9/boot-9.scm:97:6 (thrown-k . args)>
>> >> vm-error ...]
>> >> In unknown file:
>> >> ?: 5 [apply-smob/1 #<catch-closure 34725c0> vm-error ...]
>> >> In gnucash/main.scm:
>> >> 98: 4 [dumper vm-error vm-run "VM: Stack overflow" ()]
>> >> In unknown file:
>> >> ?: 3 [display-error #<stack 5e99150> #<output: file 2> ...]
>> >> In ice-9/boot-9.scm:
>> >> 106: 2 [#<procedure 54ddb80 at ice-9/boot-9.scm:97:6 (thrown-k . args)>
>> >> wrong-number-of-args ...]
>> >> 102: 1 [#<procedure 54ddc00 at ice-9/boot-9.scm:97:6 (thrown-k . args)>
>> >> wrong-number-of-args ...]
>> >> In unknown file:
>> >> ?: 0 [apply-smob/1 #<catch-closure 3472900> wrong-number-of-args ...]
>> >> root at orca:/tmp#
>> >>
>> >> The file /usr/share/gnucash/python/init.py does exist -
>> >> root at orca:/tmp# ls -alh /usr/share/gnucash/python/init.py
>> >> -rw-r--r-- 1 root root 2.8K Feb 9 08:30
>> /usr/share/gnucash/python/init.py
>> >> root at orca:/tmp#
>> >>
>> >> This same report has worked for years, and not it crashes when I change
>> >> the
>> >> date range. Any thoughts on how to fix this?
>> >>
>> >> Thanks,
>> >>
>> >> Mark
>> >> _______________________________________________
>> >> gnucash-user mailing list
>> >> gnucash-user at gnucash.org
>> >> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> >> -----
>> >> Please remember to CC this list on all your replies.
>> >> You can do this by using Reply-To-List or Reply-All.
>> >>
>> >
>> >
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
>>
>>
>>
>>
>>
>