Created attachment 858962 [details] sample file I was trying to search for the word "data" but but the time I type just 'd' in the find box, it hangs and then crashes most of the time. If it doesn't crash, then I get to type 'a' and it hangs again. Searching through slightly big files has become impossible. Attached is a sample file that's only 177 KB and it's crashing even with this one.
I don't think that gedit actually hangs, but it slows to the point that a user could reasonably mistake it as hung. Unfortunately, it appears that this case is going to be yet another where the developers ignore the problem until they can simply declare that the version for which the bug was reported is no longer maintained. A clear description of this bug is give as bug #1080751: Description of problem: As a gedit search string is entered, gedit rushes to highlight every instance conforming to whatever of the string has been entered. Thus if one attempts to search for instances of "egregious", and has entered the 'e', gedit finds and highlights every 'e' in the document. It refuses to respond to the subsequent 'g' until it has first found and highlighted every 'e'. Given a fairly large (yet not huge) document, and an ordinary machine, gedit may be unresponse for a minute or more. Version-Release number of selected component (if applicable): 3.10.3 How reproducible: Always. Steps to Reproduce: 1. Open gedit. 2. Read or generate a large document with many instances of some character. 3. Search for a string that begins with that character. Actual results: gedit unresponsive, as if frozen. Expected results: gedit continues to be constructively responsive. Additional info:
Yup, the bug is still here, with the developers pointedly looking in some other direction. I notice that the gedit rpm is at version 3.10.4-1.
This bug is over a year old, with not so much as a comment from developers.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I no longer report bugs in gedit, though I have found a more dire one than that here. (And the bug here is actually pretty d_mn'd bad!) Bugzilla may be used like voice-mail, either genuinely to facilitate communication, or simply to create an illusion of responsiveness. So far, _no_ bug that I have ever reported with bugzilla (or anything like it) has ever been fixed in a _timely_ manner, and most have simply gone unfixed, even across major versions of software. In the era before this sort of bug-reporting software became common, _most_ bugs that I reported were _quickly_ patched! My policy has become to stop reporting bugs for any piece of software where there is not a timely fix for some bug that I've reported. Arguably, I should just stop reporting bugs for any software that uses something such as bugzilla.
Hi Daniel, I think there may be a misunderstanding on the purpose and scope of bugzilla. 1) bugs like this should really go upstream to bugzilla.gnome.org. Not only is there more expertise there, but normally fixes need upstream bugs anyway before they can go in. fedora bugzilla is more for tracking distro-specific problems and problems that are being tracked for the next release. You're likely to get a more timely response in upstream bugzilla and you can tap the expertise of the people who actually write the software there. 2) But that aside, bugzilla isn't actually a mechanism for receiving support. It's just one way for members of the open source community to contribute back to the projects they use. Reports are extremely valuable and they do lead to bugs getting fixed, but there is no SLA, or expectation that a specific report will lead to a particular bug getting fixed. A bug report should be thought of as a gift or contribution to the project, not a request from the project. Anyway, mind filing this upstream?
One of the things that I've done, with bugzilla and with similar systems, is ask for guidance as to what areas of the source code I needed to examine to find where the code was going wrong. I've been quite willing to pore over the code, but it would obviously be insane for me to try to learn _everything_ from scratch. I have _never_ got an answer to such a query, though I have observed previously inert developers begin to move -- slowly -- when such a query has been made. [Insert obscenities here.] So, I'm sorry, but I don't think that your theory of this being an opportunity to contribute (beyond the contribution of reporting a bug) operationalizes very well. If this is _not_ the proper place for bugger to have reported the bug, then he-or-she should have been told as much, ab initio. Whatever Mr or Ms Bugger's over-all experience may be, the fact remains that _nothing_ that I report to systems such as this has _ever_ been fixed in a timely manner (even when I've offered to do the coding so long as someone would point me in the right general direction). I"m not sanguine about moving things upstream, after observing that yum (which should have been fixed upstream) had to be sort-of fixed downstream because of the petulance of the the upstream developer -- who was also the downstream maintainer until he took his ball and left because someone was going to patch the code ahead of his planned schedule. [Insert obscenities here.] But, in any case, no, I don't file any more bug reports about gedit, because this bug was not fixed in a timely manner. Anyone who thinks that it is important to fix this program may read my comment (right after Mr or Ms Bugger's comment), recreate the bug, and then file a report upstream. But I'm done with it.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.