This happens with kwrite in KDE 4.6.3: Steps to reproduce: - launch 'kwrite', e.g. by opening an existing text file - type Ctrl+F and enter some search criteria - create a new file or open an existing one - the search criteria is gone in the first file Not only is the search criteria gone, but the first file scrolled to another place in the document, which is 2x irritating (especially when working on very large files). As far as I can tell, this problem never appeared in previous releases of KDE/kwrite (e.g. in Mandriva Linux 2010.2).
This problem happens in both Mageia 1 (KDE 4.6.3) and Cauldron (KDE 4.7.0 RC1).
I reported the problem upstream too: https://bugs.kde.org/show_bug.cgi?id=277082
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=277082
Not a fix, but you can avoid the return to the top of the document (or where ever the cursor was before the search), by clicking on the line shown by the search result, to actually move the cursor there, before opening the second file.
CC: (none) => davidwhodgins
Is it any better with latest KDE updates in Mageia 1 or Cauldron?
Keywords: (none) => UPSTREAMCC: (none) => stormi
No, the bug is still present in KDE 4.6.5.
Assignee: bugsquad => balcaen.johnSource RPM: kwrite-4.6.3-3.mga1 => kwrite
Since july 29th (Frédéric's last comment) nothing happened to the upstream bug report
CC: (none) => marja11
Again no changes upstream @ Frédéric Is it still valid in current cauldron, too?
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Version: 1 => 2
This problem has been fixed upstream in KDE 4.10. I checked that the fix is available in Mageia 3.
Status: NEW => RESOLVEDResolution: (none) => FIXEDTarget Milestone: --- => Mageia 3