| Summary: | crash choosing a business chart type | ||
|---|---|---|---|
| Product: | [Applications] calligrachart | Reporter: | Jaime Torres <jtamate> |
| Component: | general | Assignee: | Calligra Sheets (KSpread) Bugs <calligra-sheets-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | inge, justin.zobel, sebsauer |
| Priority: | NOR | ||
| Version First Reported In: | Git | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | the requested csv file | ||
|
Description
Jaime Torres
2011-12-19 19:19:09 UTC
I could not reproduce this crash but I suspect that I am not getting the correct data into the cells. The list above contains no separators other than space... (or the bug is just fixed). Could you attach the real CSV file to the bug? It's very difficult for me to fix this if I cannot have the data that lead to the crash. Is it possible for you to attach the CSV file in question to the bug? Created attachment 70831 [details]
the requested csv file
What I do.
Create a blank spreadsheet. Import the csv.
Select all the data except the headers.
click on the chart icon and try to select an area.
The data in char is totally different from the selected data.
When I create the chart and change the chart type to polar chart normal and then to polar chart filled. crash. (also if I first choose polar chart filled and change to polar chart normal).
Ok, I can confirm the crash. Regarding the data being different, did you set the separator to 'comma' in the csv import dialog? Ups, I have two similar files and I've included the other one :-( Anyway, the crash is there. Yes, I use comma as separator. Sorry, I misunderstood your question. The data is different, but not the imported data. The data shown in the chart when I press in the Tool Options the Edit Data... button. Thank you for the crash reports. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. I can't reproduce the bug in Version 3.2.1. |