https://bugs.kde.org/show_bug.cgi?id=357206
Branimir Amidzic <m...@ambraspace.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@ambraspace.com
--- Comment #30 from Branimir Amidzic <m...@ambraspace.com> ---
I have the same problem. The bug exists in several versions.
My current config:
KDE Plasma: 5.14.5
KDE FW: 5.54.0
Qt: 5.11.3
Gentoo stable 64bit
Kernel: 4.19.23
ambra@toshiba ~ $ balooctl indexSize
Actual Size: 3,03 GiB
Expected Size: 2,16 GiB
PostingDB: 602,46 MiB 27.288 %
PositionDB: 921,75 MiB 41.750 %
DocTerms: 296,18 MiB 13.415 %
DocFilenameTerms: 18,70 MiB 0.847 %
DocXattrTerms: 4,00 KiB 0.000 %
IdTree: 2,48 MiB 0.112 %
IdFileName: 13,74 MiB 0.622 %
DocTime: 6,88 MiB 0.311 %
DocData: 21,35 MiB 0.967 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 4,94 MiB 0.224 %
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f171c00f800 (LWP 29540))]
Thread 3 (Thread 0x7f170f38c700 (LWP 29542)):
[KCrash Handler]
#6 0x00007f1719a80c01 in ?? () from /lib64/libc.so.6
#7 0x00007f171b02dae3 in ?? () from /usr/lib64/libKF5BalooEngine.so.5
#8 0x00007f171b01f2b4 in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib64/libKF5BalooEngine.so.5
#9 0x00007f171b02b1e0 in Baloo::WriteTransaction::commit() () from
/usr/lib64/libKF5BalooEngine.so.5
#10 0x00007f171b0248d2 in Baloo::Transaction::commit() () from
/usr/lib64/libKF5BalooEngine.so.5
#11 0x000055e1d9aab577 in ?? ()
#12 0x00007f171a50b0e1 in ?? () from /usr/lib64/libQt5Core.so.5
#13 0x00007f171a51354f in ?? () from /usr/lib64/libQt5Core.so.5
#14 0x00007f17178e896a in start_thread () from /lib64/libpthread.so.0
#15 0x00007f1719a1b1af in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7f170fd8e700 (LWP 29541)):
#0 0x00007f1715ecdea4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1 0x00007f1715e87528 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2 0x00007f1715e87f0b in ?? () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f1715e880ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4 0x00007f171a6fb12b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQt5Core.so.5
#5 0x00007f171a6a711a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQt5Core.so.5
#6 0x00007f171a509aea in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7 0x00007f171b24ade5 in ?? () from /usr/lib64/libQt5DBus.so.5
#8 0x00007f171a51354f in ?? () from /usr/lib64/libQt5Core.so.5
#9 0x00007f17178e896a in start_thread () from /lib64/libpthread.so.0
#10 0x00007f1719a1b1af in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7f171c00f800 (LWP 29540)):
#0 0x00007f1719a0f5d3 in poll () from /lib64/libc.so.6
#1 0x00007f1715e87fd9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f1715e880ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3 0x00007f171a6fb12b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQt5Core.so.5
#4 0x00007f171a6a711a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQt5Core.so.5
#5 0x00007f171a6afb00 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#6 0x000055e1d9aa071c in ?? ()
#7 0x00007f1719938ae7 in __libc_start_main () from /lib64/libc.so.6
#8 0x000055e1d9aa098a in ?? ()
--
You are receiving this mail because:
You are watching all bug changes.
