Bug 298772

Summary: Changes in the middle of datafile causes Kst to crash
Product: [Applications] kst Reporter: Federico Conci <concifederico>
Component: plottingAssignee: kst
Status: RESOLVED WORKSFORME    
Severity: crash CC: netterfield, syntheticpp
Priority: NOR    
Version: 2.0.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Federico Conci 2012-04-24 23:20:55 UTC
Kst crashes if registers in the middle of the file are changed after plot is done.
It does not happen if some data is appended at EOF.

Reproducible: Always

Steps to Reproduce:
1. Plott datafile.
2. Open datafile with a text editor.
3. Modify some existing data.
4. Save datafile.
5. Crash.
Actual Results:  
Program unexpectedly closes.

Expected Results:  
The change should be reflected in plot.

Ubuntu 11.10, CSV datafile.
Comment 1 Peter Kümmel 2012-04-25 18:11:28 UTC
Replaced the spaces in gyrodata with commas but could not reproduce on Windows.
Comment 2 Netterfield 2012-04-25 22:12:02 UTC
I also can't reproduce.  It is possible that some of my recent changes in the ascii source and datavector have fixed it.

Federico, can you check it with the release candidate for 2.0.5?
Comment 3 Federico Conci 2012-04-26 12:04:34 UTC
I cant be sure I have 2.0.5 since when I go to About.. it displays
2.0.x. However, I did:
sudo apt-get autoremove kst2
sudo apt-get install kst2
and while installing again, I've seen some 2.0.5 in the libraries
upgrades. So I should not assume but it seems to be updated. Sorry,
I'm just learning..
Now, I tried to replace datapoints and crashes do not happen always
but they still happen. I managed to crash 3 times. Sometimes it does
not crash but it does not update so I have to reload the datafile
manually. Pls gimme some days and I'll try to reproduce the scenario
and bring all the details.

2012/4/25, netterfield@astro.utoronto.ca <netterfield@astro.utoronto.ca>:
> https://bugs.kde.org/show_bug.cgi?id=298772
>
> netterfield@astro.utoronto.ca changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|
> |netterfield@astro.utoronto.
>                    |                            |ca
>
> --- Comment #2 from netterfield@astro.utoronto.ca ---
> I also can't reproduce.  It is possible that some of my recent changes in
> the
> ascii source and datavector have fixed it.
>
> Federico, can you check it with the release candidate for 2.0.5?
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
> _______________________________________________
> Kst mailing list
> Kst@kde.org
> https://mail.kde.org/mailman/listinfo/kst
>
Comment 4 Andrew Crouthamel 2018-10-29 22:34:55 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-13 14:37:58 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2018-11-29 09:39:32 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!