[Bug 1064133] New: Recoll text search is unusably sluggish in Tumbleweed
http://bugzilla.opensuse.org/show_bug.cgi?id=1064133 Bug ID: 1064133 Summary: Recoll text search is unusably sluggish in Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: timothyadams@ymail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 745016 --> http://bugzilla.opensuse.org/attachment.cgi?id=745016&action=edit Recoll screen Recoll text search is almost unusably sluggish. If I enter a search term, I almost immediately see the number of 'hits' at lower left, but may wait half a minute for the first results to appear onscreen. Further, clicking 'next' for additional results also produces a long delay. If I expand or minimize the Recoll window while the database is 'hanging' in this fashion, the screen breaks up, as in the example at: https://i.imgur.com/eNVUwoh.jpg (Also included as an attachment.) I have deleted recoll.conf in ~/.config/Recoll.org, as suggested on the Recoll help page. I am using Recoll 1.23.1 + Xapian 1.4.4. Recoll 1.21.5 + Xapian 1.2.22 works fine in a Linux Mint 18.2 virtual machine on the same computer. For now, that is my only way of using Recoll: fire up the VB and search in Mint, as I did before changing to Tumbleweed! I believe this problem is unrelated to my separate bugzilla post, at: https://bugzilla.opensuse.org/show_bug.cgi?id=1064131 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1064133 http://bugzilla.opensuse.org/show_bug.cgi?id=1064133#c1 --- Comment #1 from T Adams <timothyadams@ymail.com> --- Another screenshot showing the same screen 'freeze,' or tearing: https://i.imgur.com/3xTlUBy.jpg FWIW: I do not have this problem with any other program in my openSUSE Tumbleweed installation. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1064133 http://bugzilla.opensuse.org/show_bug.cgi?id=1064133#c2 --- Comment #2 from T Adams <timothyadams@ymail.com> --- Recoll developer Jean-François Dockes was kind enough to respond to a personal email regarding this issue. He noted that Recoll uses a Webkit object to display results, and suggested I consider building the program with the --disable-webkit switch. I looked at the documentation for building the program, and decided that this effort would be beyond my skill level. However, I tried another troubleshooting step on my own: I installed Recoll under openSUSE Tumbleweed on a portable computer with an integrated graphics controller, and indexed a copy of the same drive (with 100,000+ files). The results were identical to those described in the first two paragraphs of this ticket: immediate display of number of hits, looong delays to show results, and screen fragmentation. The installation on the portable is _not_ in a virtual machine, and the portable does not have an nvidia driver. YAST2 in openSUSE indicates that I have libwebkit2gtk-4_0-37 installed, and that libwebkitgtk-1_0-0 is available in the repository. For now, I will continue indexing the drive with Recoll in the Linux Mint virtual machine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1064133 http://bugzilla.opensuse.org/show_bug.cgi?id=1064133#c3 --- Comment #3 from T Adams <timothyadams@ymail.com> --- Problem fixed by following 2017-12-08 News tip offered at the http://www.lesbonscomptes.com/recoll/ home page: Uncheck: Preferences->GUI configuration->Search parameters->Dynamically build abstracts. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1064133 http://bugzilla.opensuse.org/show_bug.cgi?id=1064133#c4 T Adams <timothyadams@ymail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from T Adams <timothyadams@ymail.com> --- I noticed after logging in that this bug is still open. It shouldn't be; it was fixed a long time ago. Apologies for not changing the status. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com