Bug 360625 - baloo crashes after KDE loads
Summary: baloo crashes after KDE loads
Status: RESOLVED DUPLICATE of bug 361727
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.20.0
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-03-16 18:29 UTC by Alan Aversa
Modified: 2016-09-11 11:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Aversa 2016-03-16 18:29:43 UTC
Application: baloo_file_extractor (5.20.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.5 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
I had just started KDE with "startx".

- Unusual behavior I noticed:
None

- Custom settings of the application:
In the past, baloo hasn't been working, so I'm thinking my system needs to be reindexed. I can't even search for anything in the KDE menu, either, due to baloo not having finished indexing in the past before crashing.

The crash can be reproduced every time.

-- 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 0x7f2b2026d7c0 (LWP 2524))]

Thread 2 (Thread 0x7f2b121f6700 (LWP 2525)):
#0  0x00007f2b1c7df30d in poll () at /lib64/libc.so.6
#1  0x00007f2b173af102 in  () at /usr/lib64/libxcb.so.1
#2  0x00007f2b173b0c8f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007f2b144324b9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f2b1d3e7f3f in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007f2b1b2b2684 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f2b1c7eaefd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f2b2026d7c0 (LWP 2524)):
[KCrash Handler]
#6  0x00007f2b10786932 in _opf_label_get_by_lang () at /usr/lib64/libepub.so.0
#7  0x00007f2b10783509 in epub_tit_next () at /usr/lib64/libepub.so.0
#8  0x00007f2b1098e0e4 in  () at /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so
#9  0x0000000000409318 in  ()
#10 0x000000000040999f in  ()
#11 0x00007f2b1d5f1648 in  () at /usr/lib64/libQt5Core.so.5
#12 0x00007f2b1d5e5f2b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#13 0x00007f2b1e2ca11c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#14 0x00007f2b1e2cf236 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#15 0x00007f2b1d5b83f3 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#16 0x00007f2b1d60aacd in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#17 0x00007f2b1d60b019 in  () at /usr/lib64/libQt5Core.so.5
#18 0x00007f2b1ab64787 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#19 0x00007f2b1ab649b8 in  () at /usr/lib64/libglib-2.0.so.0
#20 0x00007f2b1ab64a5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#21 0x00007f2b1d60bc1f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#22 0x00007f2b1d5b5f5a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#23 0x00007f2b1d5bdaed in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#24 0x000000000040839c in  ()
#25 0x00007f2b1c7047d0 in __libc_start_main () at /lib64/libc.so.6
#26 0x0000000000408459 in _start ()

Reported using DrKonqi
Comment 1 Christoph Cullmann 2016-09-11 11:26:16 UTC

*** This bug has been marked as a duplicate of bug 361727 ***