https://bugs.kde.org/show_bug.cgi?id=356389
Andrew Crouthamel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=356389
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #4 from Andrew Croutham
https://bugs.kde.org/show_bug.cgi?id=356389
--- Comment #3 from Andrew Crouthamel ---
Hello! This project has been replaced with a newer system so I will be closing
this bug. If you could please re-test on the latest Baloo. If the issue still
present, please open a new bug under "frameworks-baloo
https://bugs.kde.org/show_bug.cgi?id=356389
--- Comment #2 from eric ---
(In reply to Vishesh Handa from comment #1)
> Could you please provide a backtrace?
>
> Perhaps you could start baloo manually via gdb? First kill `baloo_file` and
> then start it via `gdb baloo_file` and then 'start'. When
https://bugs.kde.org/show_bug.cgi?id=356389
Vishesh Handa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
