Bug 233812

Summary: Kwrite / Kate : search and then left click in the editor erase the selected text
Product: [Applications] kate Reporter: Jean-Christophe Baptiste <jc>
Component: kwriteAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: gary4gar
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jean-Christophe Baptiste 2010-04-09 11:11:20 UTC
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

I can reproduce it easily :

 - open any text document with either Kate or Kwrite
 - search for a string and press next
 - click back to the text area to edit

The last highlighted text is then deleted, which can lead to serious data corruption if you are not aware !
Comment 1 Gaurish 2010-04-09 18:02:10 UTC
what's  your point? I fail to see anything unusual here. the selected text is not deleted here.
Comment 2 Jean-Christophe Baptiste 2010-04-09 19:53:45 UTC
My point is that here the text is deleted.
It does not happen with other editors, so I don't think it comes from my system settings.
There must be a bug somewhere.
Comment 3 Jean-Christophe Baptiste 2010-04-10 18:33:16 UTC
Please take this bug seriously.
Or do you mean that because you don't see the bug on your computer, it can't exist ?
Comment 4 Erlend Hamberg 2010-04-10 18:47:50 UTC
> Please take this bug seriously.
> Or do you mean that because you don't see the bug on your computer, it can't
> exist ?

no one has said that.

>  - click back to the text area to edit

what do you mean by this? click with the mouse in the text area without closing the find dialogue?
(i can't reproduce the bug here by doing that.)
Comment 5 Jean-Christophe Baptiste 2010-04-10 19:33:49 UTC
> >  - click back to the text area to edit
> 
> what do you mean by this? click with the mouse in the text area without closing
> the find dialogue?
> (i can't reproduce the bug here by doing that.)

Yes. I believe you when you say you can't reproduce it, but believe I can reproduce it all the time.
And it almost f** up a python program I was working on.
How can we go on ? Will I have to make a video of it ?
Comment 6 Jean-Christophe Baptiste 2010-04-10 19:46:35 UTC
I just found out another way to trigger this issue, so it is probably not due to the find function.

1. Highlight a piece of text and copy (ctrl-C)
2. Go to another app (Firefox) and paste.
3. The text was cut from Kate!

So we have a ctrl-X behaviour where ctrl-X is expected.

An alternative :
1. Highlight a piece of text and copy (ctrl-C)
2. Launch another Kwrite process
3. The highlighted text disappeared ! Without doing anything else !

There is something screwed that can lead to serious data loss. What the hell is it ???
Comment 7 Erlend Hamberg 2010-04-10 19:50:24 UTC
> Yes. I believe you when you say you can't reproduce it, but believe I can
> reproduce it all the time.

> How can we go on ? Will I have to make a video of it ?

again: no one has said they do not believe you. :)

you didn't answer my question about what you meant by “click back”.
Comment 8 Andreas Pakulat 2010-04-10 20:23:08 UTC
Hi,
(In reply to comment #6)
> I just found out another way to trigger this issue, so it is probably not due
> to the find function.
> 
> 1. Highlight a piece of text and copy (ctrl-C)
> 2. Go to another app (Firefox) and paste.
> 3. The text was cut from Kate!

What version of kwrite/kate/kdelibs are you using exactly?
Comment 9 Jean-Christophe Baptiste 2010-04-10 20:35:38 UTC
I made 2 quick video to illustrate the problem:
http://www.phocean.net/wp-content/uploads/kwrite1.mpeg
http://www.phocean.net/wp-content/uploads/kwrite2.mpeg

Kdelibs 4.3.5-0.1.1
Kwrite Version 4.3.5 (KDE 4.3.5) "release 0"
Kate Version 3.3.5

All are shipped with openSUSE 11.2 amd64 (official repo).
Comment 10 Jean-Christophe Baptiste 2010-04-11 08:25:13 UTC
Ok guys, after searching quite a lot, I found the culprit : skim/scim (for japanese input).

After uninstalling it, no more problem. This is certainly not a KDE bug, you can close it.

Thanks for looking at it ;)