GNOME Bugzilla – Bug 353450
Crash on quit during save by "window close" button
Last modified: 2018-06-29 21:11:56 UTC
Gnucash crashed on quit after the following step: - Save by clicking on save tool button - Then close by clicking on window close button - Gnucash asked wether I want to save or not changes (which is strange...) - Then crash... It's gnucash package from ubuntu edgy. Here's the backtrace: Memory status: size: 80822272 vsize: 0 resident: 80822272 share: 0 rss: 40636416 rss_rlim: 0 CPU usage: start_time: 1156874543 rtime: 0 utime: 1338 stime: 0 cutime:1310 cstime: 0 timeout: 28 it_real_value: 0 frequency: 16 Backtrace was generated from '/usr/bin/gnucash' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231042896 (LWP 10340)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71204
Thread 1 (Thread -1231042896 (LWP 10340))
Thanks for reporting this problem. After you clicked the "Save" button, did you click the "Close" button *immediately* while the saving process was still ongoing? Or are you sure the process of saving already finished? We've had problems in the past if gnucash quits while saving is still ongoing, so that's why I ask.
I don't remember, but I can replicate a crash with a similar backtrace by clicking on window close button during file saving. Gnucash pops a window asking if I want to save/discard the current document, and crash if I click on "Save". (By the way, thanks to all gnucash developpers for the 2.0 version. Very well done!)
*sigh* This exact bug has been reported as bug#334482 but we thought it had been fixed by bug#334090 already in gnucash-1.9.6. Even before that we had the similar bug#155327 but this has been fixed in gnucash-1.9.2. What's going on here? Is this one of the two fixed bugs above or yet another new one?
Oh, and just for completeness: Is your gnucash file saved in compressed form or in plaintext form? Please check the preference under "General" (or was it "File") and/or try to open your gnucash data file with a text editor. Probably it is saved in compressed form. I'm asking because the relevant failed assertion from frame#10 is shown in frame#9. It's the failed assertion in io-gncxml-v2.c:1292 which reads: /* avoid reading from file that is still being written to by a child process */ g_assert(gzip_child_pid == 0); Oops.
Mieux vaut tard que jamais... (better late than never...) I've checked the account file format, and yes, it's a compressed file.
Im' changing the version info. It's an ubuntu egdy package built from r14585.
*** Bug 372142 has been marked as a duplicate of this bug. ***
The other duplicates bug#372142 bug#372998 experience this on the first try of the program. The file is certainly saved in compressed mode there because that's the default. We really need to do something about this...
*** Bug 370236 has been marked as a duplicate of this bug. ***
*** Bug 376263 has been marked as a duplicate of this bug. ***
*** Bug 378981 has been marked as a duplicate of this bug. ***
*** Bug 376823 has been marked as a duplicate of this bug. ***
*** Bug 380270 has been marked as a duplicate of this bug. ***
Should be fixed in r15168.
Backported into 2.0 as r15175. This change will be in 2.0.3
*** Bug 381887 has been marked as a duplicate of this bug. ***
*** Bug 383738 has been marked as a duplicate of this bug. ***
*** Bug 384398 has been marked as a duplicate of this bug. ***
*** Bug 384742 has been marked as a duplicate of this bug. ***
*** Bug 385349 has been marked as a duplicate of this bug. ***
*** Bug 385264 has been marked as a duplicate of this bug. ***
*** Bug 386066 has been marked as a duplicate of this bug. ***
*** Bug 386762 has been marked as a duplicate of this bug. ***
*** Bug 387597 has been marked as a duplicate of this bug. ***
*** Bug 387917 has been marked as a duplicate of this bug. ***
*** Bug 390814 has been marked as a duplicate of this bug. ***
*** Bug 391401 has been marked as a duplicate of this bug. ***
*** Bug 391421 has been marked as a duplicate of this bug. ***
*** Bug 390399 has been marked as a duplicate of this bug. ***
*** Bug 392016 has been marked as a duplicate of this bug. ***
*** Bug 393979 has been marked as a duplicate of this bug. ***
*** Bug 422045 has been marked as a duplicate of this bug. ***
*** Bug 428903 has been marked as a duplicate of this bug. ***
*** Bug 428950 has been marked as a duplicate of this bug. ***
*** Bug 430178 has been marked as a duplicate of this bug. ***
*** Bug 431509 has been marked as a duplicate of this bug. ***
*** Bug 431808 has been marked as a duplicate of this bug. ***
*** Bug 432319 has been marked as a duplicate of this bug. ***
*** Bug 433153 has been marked as a duplicate of this bug. ***
*** Bug 438648 has been marked as a duplicate of this bug. ***
*** Bug 447241 has been marked as a duplicate of this bug. ***
*** Bug 454166 has been marked as a duplicate of this bug. ***
*** Bug 461450 has been marked as a duplicate of this bug. ***
*** Bug 465348 has been marked as a duplicate of this bug. ***
*** Bug 471455 has been marked as a duplicate of this bug. ***
*** Bug 471761 has been marked as a duplicate of this bug. ***
*** Bug 472092 has been marked as a duplicate of this bug. ***
We should add the Debian/Ubuntu team to the CC of this bug so they can push out 2.0.5. I'm sick and tired of all these poor souls using a broken release and then coming to US because their distribution is too dain-bramaged to supply an updated, fixed version.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=353450. Please update any external references or bookmarks.