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

            Bug ID: 368243
           Summary: Caída de componente kde al finalizar descarga
           Product: Baloo
           Version: unspecified
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: General
          Assignee: pinak.ah...@gmail.com
          Reporter: tomas.gonzalez.val...@gmail.com

Application: baloo_file (5.21.0)

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

-- Information about the crash:
- What I was doing when the application crashed: Estaba descargando jdveloper
desde  el sitio de oracle. Al finalizar apareció el mensaje de error. También
me falla de cuando en cuando la conexión a la wifi.

The crash can be reproduced sometimes.

-- 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 0x7fe61dd07780 (LWP 1740))]

Thread 2 (Thread 0x7fe4d2d0d700 (LWP 5958)):
#0  0x00007fe61b829bfd in poll () at /lib64/libc.so.6
#1  0x00007fe61826ae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fe61826af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fe61c457d8b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#4  0x00007fe61c3fed53 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#5  0x000000000041531b in  ()
#6  0x00007fe61c222382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007fe61c22532f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fe61a8660a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fe61b83202d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fe61dd07780 (LWP 1740)):
[KCrash Handler]
#6  0x00007fe61955625c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x00007fe61caf34cd in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x00007fe61caf0dc0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007fe61cb02949 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d453 in  ()
#11 0x000000000041de02 in  ()
#12 0x00007fe61c43073f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x000000000041e75a in  ()
#14 0x00000000004228f9 in  ()
#15 0x00007fe61c43073f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x00007fe61c4b28ee in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
#17 0x00007fe61c43da89 in QSocketNotifier::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x00007fe61c40118d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x00007fe61c400e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x00007fe61c458ca5 in  () at /usr/lib64/libQt5Core.so.5
#21 0x00007fe61826ac84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#22 0x00007fe61826aed8 in  () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fe61826af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#24 0x00007fe61c457d6c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#25 0x00007fe61c3fed53 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#26 0x00007fe61c4068f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#27 0x000000000040a832 in  ()
#28 0x00007fe61b76eb25 in __libc_start_main () at /lib64/libc.so.6
#29 0x000000000040a9a8 in _start ()

Possible duplicates by query: bug 368193, bug 359672, bug 355210, bug 353223.

Reported using DrKonqi

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

Reply via email to