112350 2005-09-10 08:53:46 +0000 kbabel freeze process after search 2006-11-11 13:25:14 +0000 1 1 10 Unmaintained kbabel KBabel editor 1.10.2 Gentoo Packages Linux RESOLVED FIXED NOR major --- 0 manolis visnovsky 0 oldest_to_newest 372033 0 manolis 2005-09-10 08:53:47 +0000 Version: 1.10.2 (using KDE KDE 3.4.2) Installed from: Gentoo Packages Compiler: gcc 3.4.4 native amd64 build system OS: Linux I open a po file in kbabel. I start a search with Ctrl+F or Edit->Find enter a term. After the first hit. I use the wheel over the message list to browse & scroll the list. I Try Find next , or F3 to find the next hit. I doesn't do anything. The search process goes at 100% cpu usage. I can click on the list to continue search normally with F3 The process of kbabel remains at 100% , and if I close it it remains open and at 100%. I have to killall -9 kbabel If in the above method if I don't scoll the message list, after the first hit. And just press F3, or edit messages there is no strange behaviour. 378494 1 nicolasg 2005-10-03 14:55:01 +0000 Increasing severity to "major" (as it is a freeze). 395442 2 manolis 2005-12-04 12:08:43 +0000 Same with kde 3.5 version of kbabel... Why this bug is still UNCONFIRMED? There is noone that can reproduce it? 485838 3 lucardus 2006-11-11 13:25:14 +0000 SVN commit 604049 by johach: Avoid endless loop if focus is taken away before "find next" operation. BUG:112350 M +1 -1 kbabelview.cpp --- branches/KDE/3.5/kdesdk/kbabel/kbabel/kbabelview.cpp #604048:604049 @@ -1959,7 +1959,7 @@ pos.part = Msgid; pos.offset = msgidLabel->currentIndex(); } - else if(msgstrEdit->hasFocus()){ + else { pos.part = Msgstr; pos.offset = msgstrEdit->currentIndex(); pos.form = msgstrEdit->currentForm();