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 611014 - CSV import crashes
CSV import crashes
Status: RESOLVED INCOMPLETE
Product: GnuCash
Classification: Other
Component: Import - Other
2.3.x
Other Windows
: Normal critical
: ---
Assigned To: Christian Stimming
Christian Stimming
Depends on:
Blocks:
 
 
Reported: 2010-02-24 21:59 UTC by Heikki Salokanto
Modified: 2018-06-29 22:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
CSV file (113 bytes, application/vnd.ms-excel)
2010-02-24 21:59 UTC, Heikki Salokanto
Details
Error in csv import dialog (46.89 KB, image/png)
2010-02-24 22:00 UTC, Heikki Salokanto
Details
CSV import dialog (44.73 KB, image/png)
2010-02-24 22:00 UTC, Heikki Salokanto
Details

Description Heikki Salokanto 2010-02-24 21:59:54 UTC
Created attachment 154629 [details]
CSV file

CSV import always crashes.

How to reproduce:
- Create default set of empty accounts
- Select File | Import | Import CSV/Fixed-Width
- Select the attached file "siirto3.csv"
- Check tab-separator and uncheck comma
- Set the 1st field as description, 2nd as deposit, 3rd as withdrawal, 4th as date (see attachment "import_dialog.png")
- Click OK
- Select eg. Assets | Current assets | Savings account as the account

At this point, depending on which field you clicked last, the field header MAY HAVE BEEN cleared (attachment "error1.png").

- To go around this error, set the fields as described above and after that, select eg. d-m-y date format and then again y-m-d. This is silly.
- Click Ok.
- BOOM!

It also crashed once when I just tried to set the fields (the date field, to be precise).

Note: To use the attached CSV file, you may need to set your default language to Finnish or some other (European) language in which comma is used as decimal separator - or just change the commas to periods in the file...
Comment 1 Heikki Salokanto 2010-02-24 22:00:26 UTC
Created attachment 154630 [details]
Error in csv import dialog
Comment 2 Heikki Salokanto 2010-02-24 22:00:49 UTC
Created attachment 154631 [details]
CSV import dialog
Comment 3 Christian Stimming 2010-03-02 12:11:02 UTC
Even though I haven't tried this example myself, I have seen plenty of crashes in the CSV importer before. Unfortunately this feature is only half-finished and we probably have to disable it for the 2.4.0 stable release. Sorry for that.
Comment 4 Phil Longstaff 2010-03-09 20:17:59 UTC
I tried this on linux - changed ',' to '.' in the csv file, and was able to import with no problem.  What platform are you running?
Comment 5 Heikki Salokanto 2010-03-09 20:26:36 UTC
(In reply to comment #4)
> I tried this on linux - changed ',' to '.' in the csv file, and was able to
> import with no problem.  What platform are you running?

Windows Vista x86_64.
Comment 6 Phil Longstaff 2010-03-14 14:30:53 UTC
Regarding the issue that sometimes the last column type switches back to "None", there seems to be a difference between linux and windows in how combo boxes are handled.  On linux, selecting an item from the dropdown is sufficient.  On windows, you need to select an item from the dropdown and then select something else in order for the new type to really register.
Comment 7 Phil Longstaff 2010-03-15 16:10:56 UTC
r18911 addresses the problem where the "Date" column is lost.
Comment 8 Christian Stimming 2010-10-16 19:49:31 UTC
I can import the attached file correctly (2.3.15 on Linux) and without any crash. This is in de_DE locale, i.e. with the comma as decimal separator. I followed the advice from above and no crash occurred, and also the date format didn't behave in any unexpected way. Still a problem with 2.3.15?
Comment 9 Christian Stimming 2010-11-01 15:15:22 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 10 John Ralls 2018-06-29 22:35:31 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=611014. Please update any external references or bookmarks.