2.0.4 Backtrace on Start-up (99% solved)

[Kevin Kleinfelter]

Based on my experiences, you have two options:
1. Go with the head of the trunk on Subversion
2. Comment-out the offending call and live without reports.

I went with option 3 - continue using Quicken and continue to monitor
development of GnuCash and KMyMoney

On 1/7/07, Pankaj Kumar Sharma <pkscwc at gmail.com> wrote:
> >I am having exactly the same problem.
> First, I have compiled the Gnucash-2.0.3 version, then I tried 2.0.4 also.
> The problem persists. Have you found some solution?
> My backtrace:
>
> Backtrace:
> In current input:
>    1: {0}* [gnc:report-menu-setup]
>    ?: 1  (letrec (# # # ...) (gnc:add-extension income-expense-menu) ...)
> In /usr/local/share/gnucash/guile-modules/gnucash/report/report-gnome.scm:
>  118: 2* [gnc:hook-run-danglers "hook_report"]
> In /usr/local/share/gnucash/scm/hooks.scm:
>   49: 3* [gnc:debug "Running functions on hook " ...
>   49: 4*  [gnc:hook-name-get "hook_report"]
>   74: 5   [vector-ref "hook_report" {0}]
>
> /usr/local/share/gnucash/scm/hooks.scm:74:3: In procedure vector-ref in
> expression (vector-ref hook 0):
> /usr/local/share/gnucash/scm/hooks.scm:74:3: Wrong type argument in position
> 2: 0
>
>
> _______________________________________________
> 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.
>