After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 453004 - Crash on startup, possibly related to scheduled transaction
Crash on startup, possibly related to scheduled transaction
Status: VERIFIED DUPLICATE of bug 443941
Product: GnuCash
Classification: Other
Component: Scheduled Transactions
2.1.x
Other Windows
: Normal critical
: ---
Assigned To: Josh Sled
Josh Sled
Depends on:
Blocks:
 
 
Reported: 2007-07-02 06:38 UTC by Vahur Lokk
Modified: 2018-06-29 21:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
data file - another try (14.98 KB, application/octet-stream)
2007-07-02 10:39 UTC, Vahur Lokk
Details

Description Vahur Lokk 2007-07-02 06:38:50 UTC
WinXP Pro, SP2
1. Created set of business accounts and localised to Estonian. 
2. Started to enter accounting data for my biz since mid-march. Generally behaved OK (had one crash during the account creation).
3. Entered rent payment and created a monthly scheduled payment based on that. OK. Had one restart, after that it created later rent payments OK.
4. Entered salary+taxes calculation (5 different splits). Created a scheduled transaction based on that, but renamed it. Restarted to have later transactions entered. Complains it cannot acquire a lock. Would not open.
5. Went to sleep and switched box off.
6. In the morning start Gnucash, it crashes.
7. Retry. Cannot get the lock.
8. Remove lck-file.
9. Now Gnucash opens. scheduled salary transaction is gone, even if I saved for sure.
10. Recreate it. Restart. Now it does not open anymore, crashes either immediately or cannot get the lock. Removing the lock file does not help.
Comment 1 Christian Stimming 2007-07-02 10:02:35 UTC
Thanks for reporting this. Do you think you can send us your data file ("create a new attachment" below)? That would help a lot. If not, we have to come up with some other idea on how we can reproduce that problem.
Comment 2 Vahur Lokk 2007-07-02 10:39:50 UTC
Created attachment 91017 [details]
data file - another try
Comment 3 Josh Sled 2007-07-03 22:56:48 UTC
The Comment#2 datafile doesn't crash for me ... though I do notice that the transactions in the "Vahur Lokk palgaarvestus" SX template transaction have spaces in the values, and aren't getting created with actual values...

What locale do you use the datafile in?
Comment 4 Vahur Lokk 2007-07-04 04:48:16 UTC
Yep, thats the transaction that caused the crash, I believe. 
Locale is Estonian (ET_et). It seems, spaces get created as thousands separators, but then GC in some cases does not understand them this way. 
I recall that I had weird situation few times when entering/editing transactions, where it would not recognize entered amount as numerical because of these 'spaces'. Can't specify, though.
In my case I am not currently able to run Gnucash, will reinstall when 2.1.5 for Win is out.
Comment 5 Vahur Lokk 2007-07-04 15:37:03 UTC
Took some more time for further checking.
1. Made sure that whatever file I was trying to open, crashed GC immediately.
2. Moved all the XAC and log files to a separate folder and created another one for work. Discovered that older files after that opened fine.
3. Copied files one by one to work folder and ran, to identify the "last good one". In fact, the one i posted is the only one that crashes my GC even now. IIRC the only difference is in scheduling this big salary transaction - I was saving after almost every move.
Comment 6 Vahur Lokk 2007-07-04 15:56:09 UTC
One more note, then I shut up and let you work ;)
Gnucash has actually some kind of trouble with my Estonian locale. It uses dot the american way, as decimals separator, while ET should use comma for that. The rest seems fine - it uses EEK for currency, space for thousands separator etc. etc. The same was always in my Linux box, btw, makes it rather strange to enter numbers.
Comment 7 Andreas Köhler 2007-07-04 16:43:54 UTC
This bug is a duplicate of bug 443941 which has been fixed in GnuCash 2.1.5.

For a workaround, see bug 443941 comment 6.  As you compressed your data file,
you will need use a gzip-capable program (like 7zip) first to uncompress it.


*** This bug has been marked as a duplicate of 443941 ***
Comment 8 John Ralls 2018-06-29 21:41:16 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=453004. Please update any external references or bookmarks.