Bug 17890 – kate crashes on startup if current files don't exist

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Darren Davison 2003-03-20 14:09:43 UTC]

if kate is closed with files open it re-opens them when next started.  If the files are 
deleted after kate is closed, it crashes (SIGSERV 11) on restart. 

Reproducible: Always
Steps to Reproduce:
1. start kate 
2. open a file 
3. close kate 
4. delete the file 
5. re-start kate 
Actual Results:  
kate crashes 

Expected Results:  
kate starts but simply takes no action on the file that has been deleted 

the only way to get kate to start is to restore the file (or at least a file with the same 
name and path) or to edit ~/.kde/share/config/katesessionrc and remove the offending 
filename(s) from the line "current file=..."

[Comment 1 Gregorio Guidi (RETIRED) 2003-03-20 15:57:24 UTC]

From kde 3.1.1 Changelog: 
kate: 
... 
Fixed crash after starting up with a non-existant directory in the file selector history 
 
So maybe it's already fixed? 
 

[Comment 2 Dan Armak (RETIRED) 2003-03-22 13:07:08 UTC]

I can't reproduce. Please test with kde 3.1.1 (assuming you were using kde 3.1.0? if this isn't 
to be closed, provide the outupt of emerge info too). 

[Comment 3 Paul de Vrieze (RETIRED) 2003-04-24 15:32:15 UTC]

I suppose it works now.