GNOME Bugzilla – Bug 623801
gnucash file is not saved
Last modified: 2018-06-29 22:41:42 UTC
I'm using gnucash nightly build. Few Days ago gnucash is not saved the gnucash file. My env is Windows 7 Ulimate 64bit Korean version gnucash nightly version every day download (because mysql backend) Problem 1. If I click the save button, then gnucash file is deleted. case 1. gnucash file usb hdd, gnucash file deleted case 2. I copy the file to the local hdd, gnucash file deleted. I think 1 week ago "Save" Action has no problem. Problem 2. save as to mysql backend I saw the error meesage, not connected the mysql server. Please Help me!!
Thank you for reporting this bug. It would help us a lot if you could trace back which nightly build introduces this probem. Can you install previous versions of the nightly build to figure this out ?
I'm using gnucash-2.3.14-svn-r19335-setup.exe gnucash-2.3.14-svn-r19339-setup.exe Same problem occurred. I find the error log, but I can't find the log file. tell me the error tracing method. I will try the previous version tonight in KST. I think this problem is not language problem. I tried the english folder name and file name, but gnucash doesn't save the file. thank you.
http://wiki.gnucash.org/wiki/Tracefile explains what sort of trace output we have. Also, please check whether this even occurred with the 2.3.13 and earlier versions.
Created attachment 165887 [details] trace file 1
Created attachment 165888 [details] trace file 2
Created attachment 165889 [details] trace file 3
Created attachment 165890 [details] trace file 4
gnucash-2.3.14-svn-r19363-setup.exe - gnucash file is not saved. gnucash-2.3.14-svn-r19233-setup.exe - gnucash file is saved with no problem. check the attached trace file.
gnucash-2.3.14-svn-r19233-setup.exe - mysql back end is not saved gnucash data. check the attached trace file.
Created attachment 165891 [details] mysql save problem trace file
Thanks for the trace files. There is already one interesting error: * CRIT <gnc.account> [xaccAccountStringToType()] asked to translate unknown account type string 소득. which means there is probably some encoding issue somewhere in the SQL code. (@Phil?) However, I don't understand your original problem report. Do you want to save into a MySQL database? This means you do *not* save into a *file*, but instead you have a MySQL database server up and running somewhere on your computer or in your network, and you have set up a username and password and database on that MySQL server. Or do you want to save into a *file* but using SQL? In that case, we are talking about a "sqlite" file and the sqlite backend, but not MySQL.
My report means First problem, I want to save GnuCash "File", but I can't save the GnuCash File. relation trace file is 1~4 tracer file. and additional problem is gnucash can't save using mysql databae. I can connect the mysql gnucash database using Mysql Workbench, but I can't connect to Mysql database using gnucash. At another XP PC, I can using Mysql database using Gnucash. relation trace file is mysql tracer file.
Can you please make a separate bug report for the mysql problem ? I believe it's unrelated to your original problem of being unable to save to a file. Having separate bugs makes it easer to track each problem independently.
I separate bugs report for the mysql problem...(Bug 624465)
Comment on attachment 165891 [details] mysql save problem trace file Obsoleting the mysql issue trace file. That is now followed up in bug 624465.
Resetting the component to Windows. The OP fails to save an xml data file on Windows 7 ultimate, 64-bit, using a recent nightly build. Trace file 3 and 4 have log messages indicating the files being opened are not sqlite, so it looks like the files are xml. @choiks: Can you give a little more detail about the trace files ? I mean what did you do before you got the trace file ? Trace file 1 and 2 are very similar, and 3 and 4 are very similar as well. It would be useful to know what you did in GnuCash for each trace file separately (like start gnucash, choose open file, find my datafile on the usb stick, ...). Also, did you uninstall GnuCash before you installed a more recent version ?
My test step 1. Uninstall the gnucash previous version. 2. Install the gnucash using "gnucash-2.3.14-svn-r19370-setup.exe" 3. Run the gnucash (no gnucash file occured) 4. Make New file with all accounts. 5. Save as the file Data Format: xml Name: test.gnucash Folder: desktop ==> Only 1 file maked, file name is "test.gnucash.LCK" 6. make one transaction ==> log file maked, file name is "test.gnucash.20100716015422.log" 7. close gnucash ==> log file maked, file name is "test.gnucash.20100716015533.log" 2 log files and 1 trace log file attached.
Created attachment 165977 [details] one transaction log file
Created attachment 165978 [details] close log file
Created attachment 165979 [details] trace log file
trace log file translate 루트 계정 = Root 스타일 시트를 저장할 수 없음 = can't save the style sheet
Thanks for the details. I would like to figure out which nightly build breaks this behaviour. From comment #8 I see that r19233 works and r19363 doesn't. There are 33 nightly builds in between and I can't guess from your information which version is the last one that works ok and which one is the first one that doesn't work. Would you be willing to help us find exactly which revision does break the save file ? You could do this by installing a nightly build right in the middle between the two mentioned above. If this one works, install the nightly build between this one and the last one, otherwise install the one between the first one and this one and then repeat again. In about 8 iterations, you should be able to determine exactly which is the last version that worked and the first version that didn't. If you have those two versions, can you run the steps you described in each version and attach a trace file ? The transaction log files aren't necessary.
I test the nightly version. 192233 - save ok 192260 - save ok 192271 - save ok 192274 - save ok 192275 - save ok 192280 - save not ok but 192275 trace file and 192280 trace file is same. trace file attached
Created attachment 166078 [details] 192275 trace file
Created attachment 166079 [details] 192280 trace file
Thank you for tracking the first bad nightly build. Based on this, I suspect the problem starts in r19278. This revision has modifications in the xml backend and hence can cause this. I don't have the opportunity to investigate this right now, but will look at it later. Unfortunately, I don't have a Windows 7 to test with, and hence can't reproduce the error. I'll see what I can do...
if you make bug fix revision, then I test the version. I need no saving error version. Thank you.
I am looking at the code changes in r19278, but I can't find anything obvious that would cause this behaviour. Can you run the following test with any gnucash version later than 19278: * Open a windows command prompt * Run gnucash from within this prompt with some additional parameters: "c:\Program Files\gnucash\bin\gnucash" --log gnc.backend=info Of course, if you have installed gnucash in another path, please use that path * Open a file (or create a new one) * Make some changes and attempt to save the file * Attach the log file to this bug report
I test the gnucash-2.3.14-svn-r19403-setup version see the attached log file.
Created attachment 167204 [details] info log file
Thank you for the log file. I think I have found the bug now and have fixed it in r19407. For the record: the bug was introduced with the new configuration option to never keep log files. When this option was set, the data file itself got removed together with any log files. This issue is not limited to windows, it could easily be reproduced on linux. Can you test with tomorrow's nightly build ?
I download the r19408 nightly version from http://code.gnucash.org/builds/win32/trunk/. But I run the gnucash, gnucash version is r19403. and file is not saved. please check nightly build version.
The nightly build is bad. The compilation part failed and the packaging step packaged the previous nighly build. The compilation error should be fixed now, let's see what the next nighly build reports as version.
r19410 works fine. thank you!
Great ! Closing this bug then.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=623801. Please update any external references or bookmarks.