[kde] [Bug 347096] New: baloo crashed

Fabrizio shinonome.kobayashi at gmail.com
Sun May 3 12:54:27 BST 2015


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

            Bug ID: 347096
           Summary: baloo crashed
           Product: kde
           Version: unspecified
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: shinonome.kobayashi at gmail.com

Application: baloo_file (5.6.2)

Qt Version: 5.4.1
Operating System: Linux 4.0.0-1-desktop x86_64
Distribution: "openSUSE 20150430 (Tumbleweed) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
esporting last svn from smplayer repository (after setting up the
directory),svn is still esporting it as of now and i'll check the folder
afterward.

-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1d0aa2a900 (LWP 30432))]

Thread 2 (Thread 0x7f1cf4e27700 (LWP 30441)):
#0  0x00007f1d066ce4cd in poll () at /lib64/libc.so.6
#1  0x00007f1d05fbb322 in  () at /usr/lib64/libxcb.so.1
#2  0x00007f1d05fbcdef in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007f1cf6da3c69 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007f1d06fd797f in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007f1d00cf8484 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f1d066d6a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f1d0aa2a900 (LWP 30432)):
[KCrash Handler]
#5  0x00007f1d09cc94ef in ChertTable::find_in_block(unsigned char const*, Key,
bool, int) () at /usr/lib64/libxapian.so.22
#6  0x00007f1d09cc9f73 in ChertTable::find(Cursor*) const () at
/usr/lib64/libxapian.so.22
#7  0x00007f1d09ca60c9 in ChertCursor::find_entry(std::string const&) () at
/usr/lib64/libxapian.so.22
#8  0x00007f1d09cd04e3 in  () at /usr/lib64/libxapian.so.22
#9  0x00007f1d09cd481b in  () at /usr/lib64/libxapian.so.22
#10 0x00007f1d09cb582a in  () at /usr/lib64/libxapian.so.22
#11 0x00007f1d09c2e566 in Xapian::Document::Internal::get_value(unsigned int)
const () at /usr/lib64/libxapian.so.22
#12 0x00007f1d09c2e5cc in Xapian::Document::get_value(unsigned int) const () at
/usr/lib64/libxapian.so.22
#13 0x00007f1d09fe537a in Baloo::XapianDocument::value(int) const () at
/usr/lib64/libKF5BalooXapian.so.1
#14 0x000000000041fb13 in
Baloo::BasicIndexingQueue::shouldIndex(Baloo::FileMapping&, QString const&)
const ()
#15 0x0000000000420672 in
Baloo::BasicIndexingQueue::process(Baloo::FileMapping&,
QFlags<Baloo::UpdateDirFlag>) ()
#16 0x0000000000420bd4 in Baloo::BasicIndexingQueue::processNextIteration() ()
#17 0x00007f1d071e25c6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x00007f1d07e79b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x00007f1d07e7ea26 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x00007f1d071b1f45 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#21 0x00007f1d071b3ddf in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#22 0x00007f1d07209e13 in  () at /usr/lib64/libQt5Core.so.5
#23 0x00007f1d0058bc74 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#24 0x00007f1d0058bec8 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x00007f1d0058bf6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#26 0x00007f1d0720928c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#27 0x00007f1d071afe9b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#28 0x00007f1d071b7526 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#29 0x0000000000418e2f in main ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list