Bug 297569

Summary:	Meta data is imported from a previous session
Product:	[Applications] kst	Reporter:	Ben Lewis <benlewis003>
Component:	general	Assignee:	kst
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nicolas.brisset
Priority:	NOR
Version:	2.0.4
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ben Lewis 2012-04-06 06:21:55 UTC

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Build Identifier: 

When generating a new vector from a blank kst session meta data from a previous session is imported.

Reproducible: Always

Steps to Reproduce:
1. Open an ASCII data file containing meta data in the header
2. Save the kst session.
3. Select File > Close or restart kst to get a blank session
4. Use Create > Vector to generate a new vector
3. Save the session
4. Close and reopen kst
5. In the data manager there is meta data imported from the data file used in the first kst session
Actual Results:  
Meta data from a previous kst session is imported

Expected Results:  
Only meta data from data files contained in the current session should be imported

Comment 1 Nicolas Brisset 2012-04-14 19:00:38 UTC

I have not tried this yet and I'm not sure I understand it. It may be linked with the fact that we add the header lines of an ASCII file as strings when we load an ASCII file. Or possibly with the off-by-one error Barth just fixed.
Barth, is the problem still here after your last fix and if yes do you already know how to fix it? I see potential for problems according to how datasource strings are saved and reloaded...

Comment 2 Andrew Crouthamel 2018-11-06 15:12:37 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 3 Andrew Crouthamel 2018-11-18 03:28:49 UTC

Dear Bug Submitter,

This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

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

Comment 4 Justin Zobel 2022-12-20 22:51:56 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2023-01-04 05:26:10 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 2023-01-19 05:16:29 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!