Hi Sherlock,
Yes, it sounds exactly like the issue on Mint.
As stated at the end of the message, I had to resend WITHOUT the trace,
as the list rejected the message as containing a virus. So no
attachments were sent, that allowed the message to get through.
Hopefully someone else can get a trace through to the list. (Happy to
send it directly to someone if that helps.)
Regards,
Jeff.
On 20/10/25 15:50, Sherlock wrote:
Hi Jeff,
Your attachment doesn't appear to have made it but the issue sounds a
lot like:
https://lists.gnucash.org/pipermail/gnucash-user/2025-October/117827.html
Regards,
Sherlock
You may want to review
On 10/19/25 8:20 PM, Jeff wrote:
Hi List,
Just to add to the growing list of crash reports. Since updating to
GnuCash 5.13 I have also been experiencing regular crashes when
assigning payment for Invoice or Bill in GnuCash. Note this does not
happen every time, but at least every 3rd time a payment is
processed. (I think I also got one when I clicked on Print Invoice,
but not sure of that.
OS: Linux Endeavour
KDE Plasma: 6.4.5
QT Version: 6.10.0
Graphics: Wayland
Kernel: 6.17.3-arch2-1 (64-bit)
GnuCash: 5.13
Build ID: 5.13-unknown-commit(2025-10-15)
Back end: MySQL
I have attached the debug trace and the command line errors when
running the debug trace. (Hopefully the attachments get through and
are of some help.)
Had to remove the zipped trace files, as the message was rejected as
it was detected as a virus.
Regards,
Jeff.
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
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
[email protected]
To update your subscription preferences or to unsubscribe:
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.