GNOME Bugzilla – Bug 769571
Crash opening file from 2.6.1-2 Mint 17.3
Last modified: 2018-06-29 23:50:22 UTC
Created attachment 332814 [details] This file can open in previous version I had all my account information in a file that opens correctly in Linux Mint 17.3 and GNUCash 2.6.1-2 In a brand new system with Linux Mint 18 and GNUCash 2.6.12-1 it just crash trying to open the file. I installed again Linux Mint 17.3 in a virtual machine and I can open the file but in the host with Mint 18 it just crash with *** Error in `gnucash': free(): invalid pointer: 0x000055a80ce8ca40 ***
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
A stack trace would indeed be helpful, and you can find friendlier instructions for getting one at http://wiki.gnucash.org/wiki/Stack_Trace. Another helpful troubleshooting aid is the tracefile, see http://wiki.gnucash.org/wiki/Tracefile. Please find the tracefile from the crash and attach it here.
After reading about Stack_Trace y trying to get it work in Mint 18, I think I did it. I had to attach .crash file because when I click "Save Changes" it said "Comments cannot be longer than 65535 characters." BTW I couldn't change Bug Status because it only shows NEEDINFO and RESOLVED.
Created attachment 332825 [details] This is the result of the generated .crash file by apport
Created attachment 332826 [details] Trace file of the crash opening file
I'm able to load your file without trouble on 2.6.13 on OSX, I'll try again on Debian later today. Unfortunately the crash file doesn't have a stack trace in it (it does have a scheme exception from the python bindings, but that's not the problem here). What did you have trouble with in the Stack Trace procedure?
Opens OK in Windows 10 GnuCash 2.6.13, Ubuntu 16.04 GnuCash 2.6.12 & Debian 8.5.0 GnuCash 2.6.9 with my Sydney Australia timezone.
(In reply to John Ralls from comment #6) > I'm able to load your file without trouble on 2.6.13 on OSX, I'll try again > on Debian later today. > > Unfortunately the crash file doesn't have a stack trace in it (it does have > a scheme exception from the python bindings, but that's not the problem > here). What did you have trouble with in the Stack Trace procedure? Well... 1) I read https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces 2) I went to Distro Specific Instructions (https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/DistroSpecificInstructions) 3) That took me to Ubuntu (DebbugingProgramCrash: https://wiki.ubuntu.com/DebuggingProgramCrash) 4) I tried using apport-retrace after installing it (apport-retrace -R --gdb --sandbox system --cache ~/.apport/cache /var/crash/_usr_bin_gnucash.1000.crash) After hours of reading manpages I couldn't pass "ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath" 5) Then I tried with apport-cli, after GNUCash crashed and it generated the crash file. 6) I did install gnucash-dbg debug symbols. Then I tried gdb gnucash (as asked in https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#obtain-a-stacktrace ) but the command 'thread apply all bt' show some '??' which indicate that I'm still missing some debug symbols. Oscar
I downloaded and installed in Linux Mint 18, GNUCash 2.6.13 rev 6fe4b8f from http://ftp.us.debian.org/debian/pool/main/g/gnucash and it can open my file without problems.
(In reply to omvsj from comment #8) > > Well... > > 1) I read > https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces But ignored: > A stack trace would indeed be helpful, and you can find friendlier > instructions for getting one at http://wiki.gnucash.org/wiki/Stack_Trace. No matter, though, since (In reply to omvsj from comment #9) > I downloaded and installed in Linux Mint 18, GNUCash 2.6.13 rev 6fe4b8f from > > http://ftp.us.debian.org/debian/pool/main/g/gnucash > > and it can open my file without problems. So a 2.6.12 bug that's already fixed.
(In reply to John Ralls from comment #10) > (In reply to omvsj from comment #8) > > > > Well... > > > > 1) I read > > https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces > > But ignored: > > > A stack trace would indeed be helpful, and you can find friendlier > > instructions for getting one at http://wiki.gnucash.org/wiki/Stack_Trace. > Actually, I did it in 6) since is the same procedure but, as I stated, I still needed to install some debug symbol files. > No matter, though, since > (In reply to omvsj from comment #9) > > I downloaded and installed in Linux Mint 18, GNUCash 2.6.13 rev 6fe4b8f from > > > > http://ftp.us.debian.org/debian/pool/main/g/gnucash > > > > and it can open my file without problems. > > So a 2.6.12 bug that's already fixed. For me is fixed with Debian packages. I think it will be a matter of time for Mint to upgrade their repository.
>Actually, I did it in 6) since is the same procedure but, as I stated, I still >needed to install some debug symbol files. Nah, go ahead and paste it in without the other symbols. I can figure out what's going wrong with just the GnuCash symbols. We'd consider it fixed even if you'd built it from source. What the distros do is beyond our control.
(In reply to John Ralls from comment #12) > >Actually, I did it in 6) since is the same procedure but, as I stated, I still > >needed to install some debug symbol files. > > Nah, go ahead and paste it in without the other symbols. I can figure out > what's going wrong with just the GnuCash symbols. > > We'd consider it fixed even if you'd built it from source. What the distros > do is beyond our control. I read somewhere the problem was with scheduled transactions. 1) I did a backup and modified the scheduled transactions en LM 17.3, GNUCash 2.6.1-2 by eliminating some commas in formulas (some amounts had commas, something like 2,325). Modified file opened without problem in 2.6.12-1 2) I uninstall GNUCash 2.6.13 from Debian and purge any residual configuration file, as well with any dependencies. I reinstalled 2.6.12-1 from LM repos and ran gdb procedure with the original file which crashed again. Here is the result from gdb:
+ Trace 236509
Thread 1 (Thread 0x7ffff7f11ac0 (LWP 25296))
Perfect, thanks for doing that extra work. That's bug 764871. Resolution changed accordingly. *** This bug has been marked as a duplicate of bug 764871 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=769571. Please update any external references or bookmarks.