https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #31 from Gerson ---
yes, I confirm. After upgrading to 5.60 the bug is gone! Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #28 from Gerson ---
Great! I didn't try the patch yet, but it is great to know that it seems to
have fixed the problem. I'll try as soon as I can.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #21 from Gerson ---
since the upload limit is 4MB, I'll attach the file with an online system:
https://ufile.io/60gkivz8
The file (index.tgz) will be available for 30 days starting now.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #20 from Gerson ---
Indeed... baloo is working properly in my wife's computer, which runs Manjaro
KDE as well. The problem is that since there's no error message... we have do
dig manually for the corrupted file. But since it takes a while
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #17 from Gerson ---
sorry... my mistake. It took a while longer than usual, but the db is corrupted
again. The problem persists.
Manjaro has a baloo-git package (version 5.60)... I might try it next weekend.
But I cannot try it now on my
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #16 from Gerson ---
Today Manjaro had an update and it seems that the bug is fixed. However, baloo
itself was not updated. It seems that the bug was somewhere else, on some baloo
dependence...
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #15 from Gerson ---
Exactly. I couldn't find any corrupted files and the workaround of re-indexing
a single file is not sufficient. I've left my computer running for a few days
with terminal open after running balooctl disable + enable
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #12 from Gerson ---
Ok. Thanks. So, in my case this must take a long time to occur, since I've
never seen any error messages. I'll try running disable+enable again and leave
the terminal open for a long time to check it.
But these error
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #10 from Gerson ---
Where do you see the error messages? Directly on the terminal as outputs of the
'balooctl enable' command?
After I run 'balooctl enable', I get no error messages on the terminal, and the
search starts working properly
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #6 from Gerson ---
Created attachment 121222
--> https://bugs.kde.org/attachment.cgi?id=121222=edit
correct baloosearch results for comparison
How it looks when the db is working properly.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #5 from Gerson ---
Created attachment 121221
--> https://bugs.kde.org/attachment.cgi?id=121221=edit
baloosearch returns blank lines that match the number of expected results
Somehow the search kind of works, as every baloosearch I
https://bugs.kde.org/show_bug.cgi?id=409257
Gerson changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
12 matches
Mail list logo
