[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [frameworks-baloo] [Bug 366314] New: baloo crash on enabling or starting
From:       Alberto via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2016-07-31 20:37:14
Message-ID: bug-366314-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

            Bug ID: 366314
           Summary: baloo crash on enabling or starting
           Product: frameworks-baloo
           Version: 5.24.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: Baloo File Daemon
          Assignee: pinak.ahuja@gmail.com
          Reporter: agbaladia@telefonica.net

Application: baloo_file (5.24.0)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-2-default x86_64
Distribution: "openSUSE Tumbleweed (20160726) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I tried to enable/start the
apllication entering balooctl enable/start/restart

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 0x7fe113a508c0 (LWP 6892))]

Thread 3 (Thread 0x7fe1070b5700 (LWP 6896)):
[KCrash Handler]
#6  0x00007fe1115750a4 in __memcpy_avx_unaligned () at /lib64/libc.so.6
#7  0x00007fe112821584 in  () at /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007fe11280b9c4 in Baloo::PostingDB::get(QByteArray const&) () at
/usr/lib64/libKF5BalooEngine.so.5
#9  0x00007fe11281e62a in Baloo::WriteTransaction::commit() () at
/usr/lib64/libKF5BalooEngine.so.5
#10 0x00007fe112814d12 in Baloo::Transaction::commit() () at
/usr/lib64/libKF5BalooEngine.so.5
#11 0x00000000004104a4 in  ()
#12 0x00007fe111f2a5df in  () at /usr/lib64/libQt5Core.so.5
#13 0x00007fe111f2e2d8 in  () at /usr/lib64/libQt5Core.so.5
#14 0x00007fe11054c474 in start_thread () at /lib64/libpthread.so.0
#15 0x00007fe1115353ed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fe107bb8700 (LWP 6895)):
#0  0x00007fe11152ca1d in poll () at /lib64/libc.so.6
#1  0x00007fe10de2d056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fe10de2d16c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fe11215baeb in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#4  0x00007fe11210376a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#5  0x00007fe111f293b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007fe11331a9b5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007fe111f2e2d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fe11054c474 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fe1115353ed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fe113a508c0 (LWP 6892)):
#0  0x00007fe11152ca1d in poll () at /lib64/libc.so.6
#1  0x00007fe10de2d056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fe10de2d16c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fe11215baeb in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#4  0x00007fe11210376a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#5  0x00007fe11210bf6c in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#6  0x000000000040b45c in  ()
#7  0x00007fe11146d741 in __libc_start_main () at /lib64/libc.so.6
#8  0x000000000040b619 in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]