Bug 3427

Summary:	Quitting kate claims that all files in session have been modified
Product:	Mageia	Reporter:	Frank Griffin <ftg>
Component:	RPM Packages	Assignee:	John Balcaen <balcaen.john>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, nic
Version:	Cauldron	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA2TOO
Source RPM:	kate-4.7.3-1.mga2.x86_64.rpm	CVE:
Status comment:

Description Frank Griffin 2011-11-23 15:59:09 CET

Since the last several days, I've noticed that if I open a session in kate with existing files, work a bit and save my work, the file icons do not indicate that any file has not been saved, but if I quit, I get a popup claiming that all of them have been modified, and do I want to save them ?

After some testing, the problem only seems to occur with sessions that were created previously, probably before 4.7.3.  If you create a new session, open a file, save the session, and then quit, the problem does not occur.  But if you have a saved old session with files in it, open it, and quit without modifying anything, kate will claim that every file in the session has been modified.

I can't believe that the kate devs wouldn't have noticed this.  Is this possibly something related to our build ?  If not, I'll report it upstream.

Comment 1 Manuel Hiebel 2011-11-23 17:17:03 CET

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

I guess it's more an upstream bug, but not check.

Keywords: (none) => Triaged
Assignee: bugsquad => balcaen.john

Comment 2 John Balcaen 2011-11-23 19:54:34 CET

Well we don't have any patch in the kate package, neither relating kateparts in kdelibs so it should not be related to our build.
I'll try to reproduce tonight : i think i still have a session created during the 4.7.1 era.

CC: (none) => balcaen.john

Comment 3 Frank Griffin 2011-12-16 14:40:56 CET

It appears now to be not *all* files, but some random subset, maybe those which were added to the session prior to some point in time.

I've also noticed that for some of them there is a hidden file called .{filename}-kate-swp in the same directory, but deleting this doesn't appear to affect the errors.

Comment 4 Frank Griffin 2012-04-15 16:25:17 CEST

Still happening in current cauldron.

Comment 5 Marja Van Waes 2012-05-26 13:05:04 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Frank Griffin 2012-06-12 20:51:18 CEST

Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA2TOO

Comment 6 Marja Van Waes 2012-07-06 15:05:52 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 7 Frank Griffin 2012-07-31 16:47:44 CEST

Still happening in current cauldron.

Comment 8 Nic Baxter 2015-02-10 01:56:18 CET

Is this bug still valid?

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

CC: (none) => nic

Comment 9 Frank Griffin 2015-02-10 12:28:25 CET

No, this has been fixed for some time now.

Status: NEW => RESOLVED
Resolution: (none) => FIXED