Application: baloo_file_extractor (5.16.0) Qt Version: 5.5.1 Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: immediately after startup the system freezes and baloo_file_extractor crashes. This happens every time. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f4e7428d840 (LWP 2738))] Thread 2 (Thread 0x7f4e5e502700 (LWP 2739)): #0 0x00007f4e707bc2fd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f4e6b2c0182 in poll (__timeout=-1, __nfds=1, __fds=0x7f4e5e501c80) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x9e0470, cond=cond@entry=0x9e04b0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x00007f4e6b2c1c77 in xcb_wait_for_event (c=0x9e0470) at xcb_in.c:648 #4 0x00007f4e60eccda9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #5 0x00007f4e713c93ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x00007f4e6f8cf555 in start_thread (arg=0x7f4e5e502700) at pthread_create.c:333 #7 0x00007f4e707c7b9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f4e7428d840 (LWP 2738)): [KCrash Handler] #5 0x00007f4e706f99c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #6 0x00007f4e706fb65a in __GI_abort () at abort.c:89 #7 0x00007f4e71033b5d in __gnu_cxx::__verbose_terminate_handler() () from /lib64/libstdc++.so.6 #8 0x00007f4e710319a6 in ?? () from /lib64/libstdc++.so.6 #9 0x00007f4e710319f1 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x00007f4e71031c09 in __cxa_throw () from /lib64/libstdc++.so.6 #11 0x00007f4e713b1c22 in qBadAlloc() () from /lib64/libQt5Core.so.5 #12 0x00007f4e7142e953 in QListData::prepend() () from /lib64/libQt5Core.so.5 #13 0x00007f4e7350fd5a in Baloo::DocumentUrlDB::get(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #14 0x00007f4e735248d1 in Baloo::Transaction::documentUrl(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #15 0x000000000040c9f5 in Baloo::App::processNextFile() () #16 0x00007f4e715e58d8 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #17 0x00007f4e715da163 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #18 0x00007f4e7229041c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x00007f4e722958e6 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x00007f4e715aa77b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x00007f4e715ffd0d in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #22 0x00007f4e71600211 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x00007f4e6f13ca8a in g_main_dispatch (context=0x7f4e580016f0) at gmain.c:3122 #24 g_main_context_dispatch (context=context@entry=0x7f4e580016f0) at gmain.c:3737 #25 0x00007f4e6f13ce20 in g_main_context_iterate (context=context@entry=0x7f4e580016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #26 0x00007f4e6f13cecc in g_main_context_iteration (context=0x7f4e580016f0, may_block=1) at gmain.c:3869 #27 0x00007f4e71600eef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #28 0x00007f4e715a7f0a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #29 0x00007f4e715affec in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #30 0x000000000040b545 in main () Possible duplicates by query: bug 277629, bug 269746, bug 265865, bug 254903, bug 250301. Reported using DrKonqi
*** Bug 366319 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!