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

            Bug ID: 359999
           Summary: Baloo crashes every time
           Product: Baloo
           Version: unspecified
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: General
          Assignee: m...@vhanda.in
          Reporter: basu12...@gmail.com
                CC: pinak.ah...@gmail.com

Application: baloo_file (5.19.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Log in into a KDE session, wait a couple of seconds and it appears a dialog
saying that Baloo has crashed.

The crash can be reproduced every time.

-- Backtrace:
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 0x7f8619ad1780 (LWP 2411))]

Thread 2 (Thread 0x7f84cd83a700 (LWP 5026)):
#0  0x00007f86175e9bbd in poll () at /lib64/libc.so.6
#1  0x00007f8614028e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f8614028f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007f8618215d8b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#4  0x00007f86181bcd53 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#5  0x00000000004152cd in  ()
#6  0x00007f8617fe0382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f8617fe332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f86166240a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f86175f1fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f8619ad1780 (LWP 2411)):
[KCrash Handler]
#6  0x00007f861759cd79 in __memcpy_sse2_unaligned () at /lib64/libc.so.6
#7  0x00007f86188b1535 in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x00007f86188aedc0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007f86188c0949 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d3e3 in  ()
#11 0x000000000041d49d in  ()
#12 0x00007f86181ee73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x00000000004270d5 in  ()
#14 0x000000000041b686 in  ()
#15 0x00007f86181ee73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x00007f86181fbf22 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x00007f86181ef8bc in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x00007f86181bf18d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x00007f86181bee95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x00007f861821577d in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x00007f8618215aa1 in  () at /usr/lib64/libQt5Core.so.5
#22 0x00007f8614028c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x00007f8614028ed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x00007f8614028f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x00007f8618215d6c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#26 0x00007f86181bcd53 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#27 0x00007f86181c48f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x000000000040a832 in  ()
#29 0x00007f861752eb05 in __libc_start_main () at /lib64/libc.so.6
#30 0x000000000040a9a8 in _start ()

Possible duplicates by query: bug 359789, bug 359231, bug 358258, bug 357941,
bug 357919.

Reported using DrKonqi

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

Reply via email to