| Summary: | Baloo file indexer crashes on login | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Guido Winkelmann <guido-kdebugs> |
| Component: | Baloo File Daemon | Assignee: | Stefan Brüns <stefan.bruens> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | itsjustarumour.tech, joepolny, nate, navneetvikramtey, wereturtledev |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.70.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Guido Winkelmann
2020-06-02 20:56:34 UTC
Created attachment 129219 [details]
New crash information added by DrKonqi
baloo_file_extractor (5.70.0) using Qt 5.13.2
- What I was doing when the application crashed:
This happened when I was logging in from SDDM.
-- Backtrace (Reduced):
#5 0x00007f4bfffa1df5 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0
#6 0x00007f4bfffa3aec in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0
#7 0x00007f4bfffa6dc2 in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0
#8 0x00007f4bfffa9bfb in mdb_put () from /lib64/liblmdb.so.0.0.0
#9 0x00007f4c018485be in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /lib64/libKF5BalooEngine.so.5
Created attachment 129615 [details]
New crash information added by DrKonqi
baloo_file_extractor (5.71.0) using Qt 5.14.2
- What I was doing when the application crashed:
Logging in, loading desktop
Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2
Kernel Version: 5.0.0-32-generic
OS Type: 64-bit
Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz
Memory: 15.6 GiB of RAM
Graphics Processor: GeForce GTX 660/PCIe/SSE2
- Unusual behavior I noticed:
None.
- Custom settings of the application:
None.
-- Backtrace (Reduced):
#4 0x00007f91886e5234 in mdb_midl_xmerge () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
[...]
#8 0x00007f91886e21d9 in mdb_cursor_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#9 0x00007f91886e472b in mdb_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x00007f918bf8a7cc in Baloo::PositionDB::put(QByteArray const&, QVector<Baloo::PositionInfo> const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x00007f918bf9ecde in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
Created attachment 129710 [details]
New crash information added by DrKonqi
baloo_file_extractor (5.71.0) using Qt 5.15.0
- What I was doing when the application crashed:
Login, It started happening for a few times but then it started happening everytime
- Unusual behavior I noticed:
Crashing
- Custom settings of the application:
Never used it
-- Backtrace (Reduced):
#11 0x00007f511980c615 in mdb_cursor_put () from /usr/lib/liblmdb.so
#12 0x00007f511980f46b in mdb_put () from /usr/lib/liblmdb.so
#13 0x00007f511b2bf40e in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /usr/lib/libKF5BalooEngine.so.5
#14 0x00007f511b2cd328 in Baloo::WriteTransaction::commit() () from /usr/lib/libKF5BalooEngine.so.5
#15 0x00007f511b2c5bf2 in Baloo::Transaction::commit() () from /usr/lib/libKF5BalooEngine.so.5
Created attachment 130446 [details]
New crash information added by DrKonqi
baloo_file_extractor (5.70.0) using Qt 5.14.2
Logged in via SDDM after a cold boot and baloo crashed. Happens every time I boot.
-- Backtrace (Reduced):
#6 0x00007f9dd6b8ab34 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0
#7 0x00007f9dd6b7e715 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0
#8 0x00007f9dd6b80cc6 in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0
#9 0x00007f9dd6b83012 in mdb_page_split () from /lib64/liblmdb.so.0.0.0
#10 0x00007f9dd6b86325 in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0
*** This bug has been marked as a duplicate of bug 405284 *** |