Bug 310757

Summary:	kdevelop often suddenly ignores input in editor window, works fine otherwise.
Product:	[Applications] kdevelop	Reporter:	Christian Reiner <foss>
Component:	All editors	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	4.3.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christian Reiner 2012-11-27 13:32:52 UTC

Since upgrading kdevelop yesterday using openSUSEs KDE:Unstable:Playground repositories (it now shows version 4.4.60) I often, now and then, not clearly reproduceable encounter this issue: 

kdevelop works fine (menues etc) expect for the editing component: it ignores input. Highlichting text does work using mouse or keyboard (cursor keys), but I cannot remove, add or alter any characters. 

The only way to solve the issue is to close and restart kdevelop. 

Reproducible: Sometimes

Comment 1 Christian Reiner 2012-11-27 13:44:02 UTC

I just realize that the issue appears to depend on certain files opened in the editor: 

Whilst that file is blocked as described above (it is a css file inside a php project) other files can be edited without problem. Also, after restarting kdevelop the file stays locked now. 

Don't knwo ehy, but I have the impression that the block is a result of an attempt to recover the file. Sometimes kdevelop shows such message. This is not the case for this file, but actually I would _expect_ that this file has to be recovered after a kdevelop crash (out of other reasons). 
Maybe the recovering process gets initialized but does not really start? Or just the visualization is blocked somehow, so that kdevelop waits for user input into a non existing dialog? Sorry, just my stomach telling me this...

Comment 2 Christian Reiner 2012-11-27 13:57:53 UTC

Shame on me, I just realize the file was set to 'ReadOnly'. 

Three problems arise from this: 
1. that 'ReadOnly' checkbox is deeply hidden in the menu Editor->Tools->ReadOnly... Pretty hard to find and: why 'Tools' ?
2.) It is not otherwise shown that the file is in readonly mode. At least I fail to see such notice. 
3.) I was not informed that the file was set into readonyl mode. Why not, since it was an explicit action?

Comment 3 Kevin Funk 2012-12-22 20:30:32 UTC

Marking this as a duplicate of another issue that deals with that issue.

A visual marker is needed to show this.

*** This bug has been marked as a duplicate of bug 134854 ***