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
Igor Poboiko changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #30 from Igor Poboiko ---
(In reply to S from comment #29)
> Over here:
> https://bugzilla.suse.com/show_bug.cgi?id=1141028
> (Stefan Brüns)
> > A fix is already included in KF5.60.
He probably refers to the following commit (which I kind
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #29 from S ---
Over here:
https://bugzilla.suse.com/show_bug.cgi?id=1141028
(Stefan Brüns)
> A fix is already included in KF5.60.
--
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 #27 from S ---
(In reply to S from comment #26)
> (In reply to S from comment #25)
> > (In reply to Igor Poboiko from comment #24)
> >
> > > This patch might help: https://phabricator.kde.org/D21427.
> > > Can anyone confirm?
> >
> > Nice
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #26 from S ---
(In reply to S from comment #25)
> (In reply to Igor Poboiko from comment #24)
>
> > This patch might help: https://phabricator.kde.org/D21427.
> > Can anyone confirm?
>
> Nice work Igor! I'm building baloo5 with that patch
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #25 from S ---
(In reply to Igor Poboiko from comment #24)
> This patch might help: https://phabricator.kde.org/D21427.
> Can anyone confirm?
Nice work Igor! I'm building baloo5 with that patch now and I'll test it
throughout my workday
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #24 from Igor Poboiko ---
(In reply to Gerson from comment #21)
> 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
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #23 from Igor Poboiko ---
(In reply to Gerson from comment #21)
> 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
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #22 from S ---
(In reply to Gerson from comment #20)
> In my case, actually, it seems that the db only corrupts after I restart the
> computer.
I've noticed this too.
--
You are receiving this mail because:
You are watching all bug
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 are
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 #19 from S ---
(In reply to Igor Poboiko from comment #18)
> We would really appreciate if someone who experiences this could send us a
> corrupted "~/.local/share/baloo/index" entry.
>
> Just be aware that it will most likely contain a
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #18 from Igor Poboiko ---
We would really appreciate if someone who experiences this could send us a
corrupted "~/.local/share/baloo/index" entry.
Just be aware that it will most likely contain a lot of personal information.
If you don't
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 #14 from S ---
Thanks again Igor for the reply.
(In reply to Igor Poboiko from comment #13)
> Your problem looks like corruption of IdTreeDB, when for some reason Baloo
> "forgets" about some of the top-level directories, and then just
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #13 from Igor Poboiko ---
(In reply to S from comment #9)
> I would assume directory. :-) Here's what happened:
>
> [...]
It doesn't really matter, file or directory.
Your problem looks like corruption of IdTreeDB, when for some reason
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 #11 from S ---
(In reply to Gerson from comment #10)
> Where do you see the error messages? Directly on the terminal as outputs of
> the 'balooctl enable' command?
Yes.
> After I run 'balooctl enable', I get no error messages on the
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 #9 from S ---
> Hi Igor, thanks, would I run that command on a file or a directory?
I would assume directory. :-) Here's what happened:
==
> balooctl clear ~/Downloads && balooctl index ~/Downloads
> Clearing
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #8 from S ---
(In reply to Igor Poboiko from comment #7)
> Instead rebuilding the whole index, try performing `balooctl clear
> ~/somefile && balooctl index ~/somefile` (on some existing file inside your
> home folder)
Hi Igor, thanks,
https://bugs.kde.org/show_bug.cgi?id=409257
Igor Poboiko changed:
What|Removed |Added
CC||igor.pobo...@gmail.com
--- Comment #7 from Igor
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:
You
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 run in
https://bugs.kde.org/show_bug.cgi?id=409257
Gerson changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #3 from S ---
Created attachment 121191
--> https://bugs.kde.org/attachment.cgi?id=121191=edit
My current ~/.local/share/baloo/ directory while no results are returned
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #2 from S ---
Created attachment 121190
--> https://bugs.kde.org/attachment.cgi?id=121190=edit
App Menu search not returning any results (normally it should for this keyword)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #1 from S ---
Created attachment 121189
--> https://bugs.kde.org/attachment.cgi?id=121189=edit
Krunner not returning any results (normally it should for this keyword)
--
You are receiving this mail because:
You are watching all bug
32 matches
Mail list logo
