https://bugs.kde.org/show_bug.cgi?id=409499

--- Comment #21 from Kishore Gopalakrishnan <kishor...@gmail.com> ---
(In reply to tgnff242 from comment #20)
> Temporarily, I can make it work if I disable baloo, kill baloorunner, purge
> the cache, then re-enable baloo (which needs to issue `balooctl enable` two
> times). It stops working after re-dis/enabling baloo, or after a reboot,
> though.
> 
> baloo_file seems to crash, and baloosearch returns (an accurate number of)
> empty results too, so it's not krunner-specific. Unfortunately, my distro
> doesn't provide packages with debug symbols to give you a useful backtrace,
> so hopefully a dev can reproduce it. Also, drkonqi doesn't detect the crash,
> systemd-coredump does.
> 
> Also, it might be important to add that downgrading the baloo package to
> 5.76 isn't enough to "fix" the issue.

I also have the same issue. Here is the backtrace from my crash of baloo_file:

```
#0  0x00007f257d8a6396 in ?? () from /usr/lib/liblmdb.so
#1  0x00007f257d8a8efe in ?? () from /usr/lib/liblmdb.so
#2  0x00007f257d8a9644 in ?? () from /usr/lib/liblmdb.so
#3  0x00007f257d8a9c50 in mdb_get () from /usr/lib/liblmdb.so
#4  0x00007f257ed802a5 in Baloo::IdFilenameDB::get
(this=this@entry=0x7f257845c700, docId=<optimized out>,
docId@entry=50665500102950405)
    at /usr/src/debug/baloo-5.77.0/src/engine/idfilenamedb.cpp:83
#5  0x00007f257ed7a2fc in Baloo::DocumentUrlDB::get
(this=this@entry=0x7f257845c780, docId=docId@entry=50665500102950405)
    at /usr/src/debug/baloo-5.77.0/src/engine/documenturldb.cpp:171
#6  0x00007f257ed8b085 in Baloo::Transaction::documentUrl (this=<optimized
out>, id=50665500102950405)
    at /usr/src/debug/baloo-5.77.0/src/engine/transaction.cpp:102
#7  0x00005645d02bf8e4 in operator() (id=<optimized out>, __closure=<optimized
out>) at /usr/src/debug/baloo-5.77.0/src/file/indexcleaner.cpp:40
#8  std::__invoke_impl<bool, Baloo::IndexCleaner::run()::<lambda(quint64)>&,
long long unsigned int> (__f=...) at /usr/include/c++/10.2.0/bits/invoke.h:60
#9  std::__invoke_r<bool, Baloo::IndexCleaner::run()::<lambda(quint64)>&, long
long unsigned int> (__fn=...) at /usr/include/c++/10.2.0/bits/invoke.h:141
#10 std::_Function_handler<bool(long long unsigned int),
Baloo::IndexCleaner::run()::<lambda(quint64)> >::_M_invoke(const std::_Any_data
&, unsigned long long &&) (__functor=..., __args#0=<optimized out>) at
/usr/include/c++/10.2.0/bits/std_function.h:291
#11 0x00007f257ed924ff in std::function<bool (unsigned long
long)>::operator()(unsigned long long) const (__args#0=50665500102950405,
this=0x7f2578c5a9c0)
    at /usr/include/c++/10.2.0/bits/std_function.h:622
#12 Baloo::WriteTransaction::removeRecursively(unsigned long long,
std::function<bool (unsigned long long)> const&) (this=0x7ee570004e30, 
    parentId=50665500102950405, shouldDelete=...) at
/usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:159
#13 0x00007f257ed92557 in Baloo::WriteTransaction::removeRecursively(unsigned
long long, std::function<bool (unsigned long long)> const&) (
    this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at
/usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:166
#14 0x00007f257ed92557 in Baloo::WriteTransaction::removeRecursively(unsigned
long long, std::function<bool (unsigned long long)> const&) (
    this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at
/usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:166
#15 0x00007f257ed92557 in Baloo::WriteTransaction::removeRecursively(unsigned
long long, std::function<bool (unsigned long long)> const&) (
    this=0x7ee570004e30, parentId=50665500102950405, shouldDelete=...) at
/usr/src/debug/baloo-5.77.0/src/engine/writetransaction.cpp:166
```

The crash reporter didn't launch, but I found multiple crashes like this listed
in the output of 'coredumpctl list'. I have compiled baloo with debug symbols,
but please let me know if I should install debug symbols for any other package.
The last line (#15) kept on getting repeated in gdb for some reason; not sure
if this is important.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to