Application: baloo_file_extractor (5.55.0) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: same as before. Baloo keeps on crashing. no matter what i do. -- Backtrace: Application: Baloo extraheerder uit bestanden (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb41707e900 (LWP 6531))] Thread 3 (Thread 0x7fb3f4a52700 (LWP 6533)): #0 0x00007fb413bca19b in poll () from /lib64/libc.so.6 #1 0x00007fb4104ab1a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fb4104ab2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fb41450f7fb in QEventDispatcherGlib::processEvents (this=0x7fb3f0000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x00007fb4144b479a in QEventLoop::exec (this=this@entry=0x7fb3f4a51c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x00007fb4142d2d4a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:515 #6 0x00007fb415e4d9e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x00007fb4142d7c8d in QThreadPrivate::start (arg=0x7fb4160c0d60) at thread/qthread_unix.cpp:368 #8 0x00007fb4127ce569 in start_thread () from /lib64/libpthread.so.0 #9 0x00007fb413bd49ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb4091dd700 (LWP 6532)): #0 0x00007fb413bca19b in poll () from /lib64/libc.so.6 #1 0x00007fb40fc0b307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007fb40fc0cf3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007fb40bf95969 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007fb4142d7c8d in QThreadPrivate::start (arg=0x55ef9a851120) at thread/qthread_unix.cpp:368 #5 0x00007fb4127ce569 in start_thread () from /lib64/libpthread.so.0 #6 0x00007fb413bd49ef in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb41707e900 (LWP 6531)): [KCrash Handler] #6 _list_cmp_label_by_lang (t1=0x0, t2=0x7ffcd128eb70) at /usr/src/debug/ebook-tools-0.2.2-lp151.2.2.x86_64/src/libepub/list.c:140 #7 0x00007fb4037cd5d8 in FindNode (List=List@entry=0x55efdf7049d0, Data=Data@entry=0x7ffcd128eb70) at /usr/src/debug/ebook-tools-0.2.2-lp151.2.2.x86_64/src/libepub/linklist.c:116 #8 0x00007fb4037ccb56 in _opf_label_get_by_lang (lang=<optimized out>, label=0x55efdf7049d0, opf=<optimized out>) at /usr/src/debug/ebook-tools-0.2.2-lp151.2.2.x86_64/src/libepub/opf.c:869 #9 _opf_label_get_by_doc_lang (opf=<optimized out>, label=0x55efdf7049d0) at /usr/src/debug/ebook-tools-0.2.2-lp151.2.2.x86_64/src/libepub/opf.c:876 #10 0x00007fb4037c972c in epub_tit_next (tit=tit@entry=0x55efa40d6260) at /usr/src/debug/ebook-tools-0.2.2-lp151.2.2.x86_64/src/libepub/epub.c:473 #11 0x00007fb4037c994e in epub_get_titerator (epub=epub@entry=0x55efb40d6770, type=type@entry=TITERATOR_NAVMAP, opt=opt@entry=0) at /usr/src/debug/ebook-tools-0.2.2-lp151.2.2.x86_64/src/libepub/epub.c:556 #12 0x00007fb4039d5064 in KFileMetaData::EPubExtractor::extract (this=<optimized out>, result=0x7ffcd128edb0) at /usr/src/debug/kfilemetadata5-5.55.0-lp151.1.1.x86_64/src/extractors/epubextractor.cpp:163 #13 0x000055ef997faacb in Baloo::App::index (this=this@entry=0x7ffcd128f4e0, tr=0x55ef9aa180c0, url=..., id=id@entry=1082061175654417) at /usr/src/debug/baloo5-5.55.0-lp151.3.3.1.x86_64/src/file/extractor/app.cpp:191 #14 0x000055ef997fb40e in Baloo::App::processNextFile (this=0x7ffcd128f4e0) at /usr/src/debug/baloo5-5.55.0-lp151.3.3.1.x86_64/src/file/extractor/app.cpp:111 #15 0x00007fb4144f1fc4 in QtPrivate::QSlotObjectBase::call (a=0x7ffcd128ef00, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #16 QSingleShotTimer::timerEvent (this=0x55effd5c2b90) at kernel/qtimer.cpp:318 #17 0x00007fb4144e5eeb in QObject::event (this=0x55effd5c2b90, e=<optimized out>) at kernel/qobject.cpp:1269 #18 0x00007fb41525f3dc in QApplicationPrivate::notify_helper (this=this@entry=0x55ef9a83b340, receiver=receiver@entry=0x55effd5c2b90, e=e@entry=0x7ffcd128f1d0) at kernel/qapplication.cpp:3723 #19 0x00007fb415266ca4 in QApplication::notify (this=0x7ffcd128f4b0, receiver=0x55effd5c2b90, e=0x7ffcd128f1d0) at kernel/qapplication.cpp:3482 #20 0x00007fb4144b6768 in QCoreApplication::notifyInternal2 (receiver=0x55effd5c2b90, event=event@entry=0x7ffcd128f1d0) at kernel/qcoreapplication.cpp:1024 #21 0x00007fb41450ec7e in QCoreApplication::sendEvent (event=0x7ffcd128f1d0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #22 QTimerInfoList::activateTimers (this=0x55ef9a88cb30) at kernel/qtimerinfo_unix.cpp:643 #23 0x00007fb41450f479 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:182 #24 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:229 #25 0x00007fb4104aae87 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x00007fb4104ab230 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x00007fb4104ab2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x00007fb41450f7df in QEventDispatcherGlib::processEvents (this=0x55ef9a88a230, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x00007fb4144b479a in QEventLoop::exec (this=this@entry=0x7ffcd128f420, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #30 0x00007fb4144bd844 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1297 #31 0x000055ef997f9a9d in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/baloo5-5.55.0-lp151.3.3.1.x86_64/src/file/extractor/main.cpp:60 [Inferior 1 (process 6531) detached] Possible duplicates by query: bug 417656, bug 411627. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 406116 ***
The next time you submit a duplicate report (you did 4 times in a row, at least), I will make sure your mail address gets blacklisted.
Dear Sir Thank you for your reply. I wasn't trying to be annoying by sending the mails. I am not very familiar with bug reporting and the answers I get via the mail. For example how do I know when I see it is a duplicate (and don't send it) that somebody is still working on a solution? The only time I know something is solved, is when it doesn't crash anymore. I checked the reports and although I don't understand very much of it, I could see many differences in the text, so I send it again. I also wanted to let you know how often the problem appeared by sending the multiple mails in a short period of time. Could you at least instead of threatening me with blackmailing, give me an update on the solution of the problem. What can I do to solve this problem as it is very annoying that the program crashes and the whole system starts hanging every few minutes. With Greetings Aloys Vierstraete Op 15-02-2020 om 02:57 schreef Stefan Brüns: > https://bugs.kde.org/show_bug.cgi?id=417676 > > --- Comment #2 from Stefan Brüns <stefan.bruens@rwth-aachen.de> --- > The next time you submit a duplicate report (you did 4 times in a row, at > least), I will make sure your mail address gets blacklisted. >