Application: baloo_file_extractor (5.26.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.3-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: rebooting pc Received message baloo crashed unexpectedly. The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3b8e7038c0 (LWP 1872))] Thread 3 (Thread 0x7f3b71203700 (LWP 1927)): #0 0x00007f3b8b6943ed in poll () at /lib64/libc.so.6 #1 0x00007f3b8a273a06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x00007f3b8a273b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x00007f3b8c49924b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #4 0x00007f3b8c4485ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #5 0x00007f3b8c2a7343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x00007f3b8e81f559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x00007f3b8c2ab99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x00007f3b8abe95ca in start_thread () at /lib64/libpthread.so.0 #9 0x00007f3b8b69ff6d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f3b794a4700 (LWP 1874)): #0 0x00007f3b8b6943ed in poll () at /lib64/libc.so.6 #1 0x00007f3b861f3f80 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00007f3b861f5b79 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x00007f3b7d7b6da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x00007f3b8c2ab99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x00007f3b8abe95ca in start_thread () at /lib64/libpthread.so.0 #6 0x00007f3b8b69ff6d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f3b8e7038c0 (LWP 1872)): [KCrash Handler] #6 0x00007f3b738a8a18 in Exiv2::ValueType<unsigned int>::toLong(long) const () at /lib64/libexiv2.so.14 #7 0x00007f3b7805523b in KFileMetaData::Exiv2Extractor::add(KFileMetaData::ExtractionResult*, Exiv2::ExifData const&, KFileMetaData::Property::Property, char const*, QVariant::Type) () at /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so #8 0x00007f3b78055a06 in KFileMetaData::Exiv2Extractor::extract(KFileMetaData::ExtractionResult*) () at /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so #9 0x000055a4280e9e0b in Baloo::App::index(Baloo::Transaction*, QString const&, unsigned long long) () #10 0x000055a4280ea2de in Baloo::App::processNextFile() () #11 0x00007f3b8c47dd16 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #12 0x00007f3b8c472b8b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #13 0x00007f3b8ccdcc0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x00007f3b8cce20ef in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x00007f3b8c4497aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x00007f3b8c4987ab in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #17 0x00007f3b8c498d39 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x00007f3b8a2736ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x00007f3b8a273a70 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #20 0x00007f3b8a273b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x00007f3b8c49922f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #22 0x00007f3b8c4485ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #23 0x00007f3b8c45017c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x000055a4280e920f in main () Reported using DrKonqi
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!