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

            Bug ID: 358794
           Summary: Crash of baloo when deleting file
           Product: Baloo
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: General
          Assignee: m...@vhanda.in
          Reporter: michael.wag...@gmx.at
                CC: pinak.ah...@gmail.com

Application: baloo_file (5.15.0)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:

When deleting a file using dolphin, baloo_file was reported as crashed.
Using kubuntu 15.10 with latest updates.

ii  libbaloocore4                                 4:4.14.3-0ubuntu5            
                     amd64        Core funcationality for Baloo
ii  libbaloofiles4                                4:4.14.3-0ubuntu5            
                     amd64        Files funcationality for Baloo
ii  libbalooxapian4                               4:4.14.3-0ubuntu5            
                     amd64        Xapian funcationality for Baloo
ii  libkf5baloowidgets-bin                        4:15.08.2-0ubuntu1           
                     amd64        Wigets for use with Baloo - binaries
ii  libkf5baloowidgets5:amd64                     4:15.08.2-0ubuntu1           
                     amd64        Wigets for use with Baloo

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
#7  0x00007f39fd184f90 in QByteArray::QByteArray(char const*, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f39fd8366ce in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x00007f39fd846c19 in Baloo::WriteTransaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007f39fd83ebc2 in Baloo::Transaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x0000000000428555 in Baloo::MetadataMover::removeFileMetadata(QString
const&) ()
#12 0x00007f39fd391617 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x0000000000431d65 in Baloo::PendingFileQueue::removeFileIndex(QString
const&) ()
#14 0x0000000000426776 in Baloo::PendingFileQueue::processCache() ()
#15 0x00007f39fd391617 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f39fd39e178 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f39fd392603 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f39fd360efc in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f39fd3b709d in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f39fd3b75d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f39f9974ff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f39f9975250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f39f99752fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f39fd3b827f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f39fd35e75a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f39fd3662cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x0000000000415aec in main ()

Reported using DrKonqi

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

Reply via email to