GNOME Bugzilla – Bug 127642
Crash when entering scheduled transaction editor dialog
Last modified: 2018-06-29 20:38:58 UTC
Package: GnuCash Severity: major Version: 1.8.7 Synopsis: Crash when entering scheduled transaction editor dialog Bugzilla-Product: GnuCash Bugzilla-Component: Scheduled Transactions Description: Description of Problem: selecting "Scheduled transaction editor" causes Gnucash to segfault Steps to reproduce the problem: 1. Select Scheduled transaction editor from the actions (I think) menu (I think it's a data specific problem see additional information) Actual Results: segfault Expected Results: bring up the scheduled transaction editor to allow editting transactions How often does this happen? everytime Additional Information: I suspect that this may be a problem with the particular file that I am using since the problem does not occur if I create a new file. However, I don't really wish to migrate my data by hand. I'm looking into the XML file, but I'm not sure what may have changed that would be causing the segfault. This has been an issue with the last several versions for me. Debugging Information: Backtrace was generated from '/usr/bin/guile-1.6' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 3835)] (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)...(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)...(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)...(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)...(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)...(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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x400d3bb8 in waitpid () from /lib/libpthread.so.0
+ Trace 41981
Thread 1 (Thread 16384 (LWP 3835))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-21 21:45 ------- The original reporter (dmcgraw@watchland.org) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, jsled-gnomebugs@asynchronous.org.
This appears to be a unique stack trace according to the simple-dup-finder.
I've been unable to reproduce this; are you willing to send me your data file, privately?
Unfortunately I don't think I have the datafile that will cause it again. I'm almost positive it was an issue caused by an upgrade. I resolved the issue by removing my transactions (by hand editting the XML file) and then adding them back in through the interface. Everything has been working well since. I thought I had saved the XML that I cut out, but I can't find it now. If I do uncover it I'd be happy to send it to you. I'm marking it as closed since I doubt you'll be able to recreate it (as I've lost the damn data!) and I don't want this holding anything up. GnuCash has been working great the last month. Thanks for looking into it.
This seems like the memory-corruption issue. *** This bug has been marked as a duplicate of 106212 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=127642. Please update any external references or bookmarks.