[GNC] Repeatable crashes with 4.14 on 32-bit arm Linux
John Ralls
jralls at ceridwen.us
Sat Feb 10 21:19:40 EST 2024
> On Feb 10, 2024, at 5:19 PM, Robert Heller <heller at deepsoft.com> wrote:
>
> Always when hitting the reconcile button on a credit card account:
>
> Could not determine the accessibility bus address
> **
> gnc.gui:ERROR:/home/heller/gnucash-4.14/gnucash/gnome-utils/dialog-transfer.c:2297:gnc_xfer_dialog_run_until_done:
> assertion failed: (count == 1)
> Bail out!
> gnc.gui:ERROR:/home/heller/gnucash-4.14/gnucash/gnome-utils/dialog-transfer.c:2297:gnc_xfer_dialog_run_until_done:
> assertion failed: (count == 1)
> Could not determine the accessibility bus address
> **
> gnc.gui:ERROR:/home/heller/gnucash-4.14/gnucash/gnome-utils/dialog-transfer.c:2297:gnc_xfer_dialog_run_until_done:
> assertion failed: (count == 1)
> Bail out!
> gnc.gui:ERROR:/home/heller/gnucash-4.14/gnucash/gnome-utils/dialog-transfer.c:2297:gnc_xfer_dialog_run_until_done:
> assertion failed: (count == 1)
>
> Things work fine after restarting...
Restarting GnuCash or the computer?
The accessibility bus message probably indicates that the DBUS session has quit for some reason. That part would be external to GnuCash.
The assertion that's failing is about the result of
count = g_signal_handlers_disconnect_by_func(dialog,
gnc_xfer_dialog_response_cb,
xferData);
There should be exactly 1 handler using that gnc_xfer_dialog_response_cb connected to the signal. It there aren't either the transfer dialog is trying to run more than one instance (count > 1) or the the handler is already disconnected (count == 0). I don't think connecting or failing to connect to the accessibility bus would affect that, but I don't know what would cause it.
Regards,
John Ralls
More information about the gnucash-user
mailing list