Discussion:
[Kst] [Bug 298772] New: Changes in the middle of datafile causes Kst to crash
Federico Conci
2012-04-24 23:20:55 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

Bug ID: 298772
Severity: minor
Version: 2.0.4
Priority: NOR
Assignee: ***@kde.org
Summary: Changes in the middle of datafile causes Kst to crash
Classification: Unclassified
OS: Linux
Reporter: ***@gmail.com
Hardware: Ubuntu Packages
Status: UNCONFIRMED
Component: plotting
Product: kst

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.
--
You are receiving this mail because:
You are the assignee for the bug.
Peter Kümmel
2012-04-25 18:11:28 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

Peter Kümmel <***@gmx.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmx.net

--- Comment #1 from Peter Kümmel <***@gmx.net> ---
Replaced the spaces in gyrodata with commas but could not reproduce on Windows.
--
You are receiving this mail because:
You are the assignee for the bug.
n***@astro.utoronto.ca
2012-04-25 22:12:02 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

***@astro.utoronto.ca changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@astro.utoronto.
| |ca

--- Comment #2 from ***@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.
Federico Conci
2012-04-26 12:04:26 UTC
Permalink
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.
Post by Federico Conci
https://bugs.kde.org/show_bug.cgi?id=298772
What |Removed |Added
----------------------------------------------------------------------------
CC|
| |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 the assignee for the bug.
_______________________________________________
Kst mailing list
https://mail.kde.org/mailman/listinfo/kst
Federico Conci
2012-04-26 12:04:34 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

--- Comment #3 from Federico Conci <***@gmail.com> ---
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.
Post by Federico Conci
https://bugs.kde.org/show_bug.cgi?id=298772
What |Removed |Added
----------------------------------------------------------------------------
CC|
| |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 the assignee for the bug.
_______________________________________________
Kst mailing list
https://mail.kde.org/mailman/listinfo/kst
--
You are receiving this mail because:
You are the assignee for the bug.
Jekyll Wu
2012-11-06 03:37:16 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

Jekyll Wu <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|minor |crash
--
You are receiving this mail because:
You are the assignee for the bug.
Andrew Crouthamel
2018-10-29 22:34:55 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

Andrew Crouthamel <***@kdemail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO

--- Comment #4 from Andrew Crouthamel <***@kdemail.net> ---
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!
--
You are receiving this mail because:
You are the assignee for the bug.
Bug Janitor Service
2018-11-13 14:37:58 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=298772

--- Comment #5 from Bug Janitor Service <bug-***@kde.org> ---
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!
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...