Saving a changed GC file with scheduled transactions hangs. Maybe because a copy of the scheduled transactions is missing in the temp file(?). How to reproduce (plus some analysis): ====================================== 0 - Open a GC file with scheduled transactions, apply a change and hit the save button. Usually the save progress bar is completed twice now. 1 - The first save progress bar is completed without any problem. 2 - A temp file (named '<GC file name>.tmp-axxxxx') next to the GC file is created. It does contain an xml element <gnc:count-data cd:type="schedxaction">3</gnc:count-data> (here: 3 as an example) indicating the number of scheduled transactions in the GC file to be saved, BUT it does **not** contain any xml element <gnc:schedxaction version="2.0.0"> ... </gnc:schedxaction> 3 - The save progress bar is restarted, but hangs until eternity after, say, the first third of the progress bar. 4 - GC cannot be properly exited. I need to kill the process. Thus I cannot change and save a GC file with scheduled transactions any more. This is the reason I cannot provide any simple sample. Way-out (not a workaround) ========================== Manually removing all <gnc:schedxaction> elments and the counter element <gnc:count-data cd:type="schedxaction"> from the GC file helps: then it **can** be saved without any problem. Currently installed =================== nightly build gnucash-3.3-2018-12-10-git-3.3-170-g9921ab22a+.setup.exe on Windows 10. Since I am not sure if this a typical Windows issue, I assigned this bug to the component 'Windows'. Thanks!
I can't replicate this. Please attach a sample file that demonstrates the problem.
Is this at all related to your bug 796962?
(In reply to John Ralls from comment #1) > I can't replicate this. Please attach a sample file that demonstrates the > problem. I tried to explain that I cannot save any file showing the problem so that I am unable to create a minimal culprit example, unfortunately. Would it be OK for you if I sent you a real life file via private email? (In reply to John Ralls from comment #2) > Is this at all related to your bug 796962? Yes.
> Would it be OK for you if I sent you a real life file via private email? Sure. Is it related enough that we don't need both?
I loaded your file with GnuCash 3.3 and created a duplicate of "für Monat 07; Gewinnsparrate 0112578115" in Mama-Aktiva:Finanzkonten:Sparda-Bank SW:Girokonto, then saved the file. No problems. On the off chance that there was a localization problem I repeated the experiment after setting my Windows locale to Deutsch-Deutschland. Still worked fine. Try creating a new user and running GnuCash when logged in as that user.
(In reply to John Ralls from comment #5) Thank you for looking into that, John! > On the off chance that there was a localization problem I repeated the > experiment after setting my Windows locale to Deutsch-Deutschland. Still > worked fine. Hmm. I 'set LC_ALL=C' before calling GC, but no success either. Now the issue becomes a bit more bizarre: I tried to save the file from which I removed the scheduled transaction related XML elements after some changes. Now this does not work. Thus there must be another reason for that I guess.
Did you try with a new user?
Try running GnuCash from the command line with --log gnc.backend.xml=debug. Unfortunately there aren't a lot of debug messages, but it still might provide a clue about where it's hanging.
Appears to be solved in GC 3.5 (or earlier). Many thanks to all the devels taking care of this!
