[kde] [Bug 347599] New: Testing if the Baloo product and component are correctly set
Vishesh Handa
me at vhanda.in
Tue May 12 12:13:47 BST 2015
https://bugs.kde.org/show_bug.cgi?id=347599
Bug ID: 347599
Summary: Testing if the Baloo product and component are
correctly set
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: me at vhanda.in
Application: baloo_file (5.9.90)
(Compiled from sources)
Qt Version: 5.4.1
Operating System: Linux 3.19.3-3-ARCH x86_64
Distribution: "Arch Linux"
-- Information about the crash:
- What I was doing when the application crashed:
Alright. I hope this works. Also it is quite bad that I haven't been getting
baloo crash reports.
-- Backtrace:
Application: Baloo File (baloo_file), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f61e33b5800 (LWP 3269))]
Thread 2 (Thread 0x7f61e223d700 (LWP 3270)):
#0 0x00007f61efe6d4ed in poll () from /usr/lib/libc.so.6
#1 0x00007f61ef7609f2 in ?? () from /usr/lib/libxcb.so.1
#2 0x00007f61ef76256f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3 0x00007f61e3326399 in ?? () from /usr/lib/qt/plugins/platforms/libqxcb.so
#4 0x00007f61f09fe56e in ?? () from /usr/lib/libQt5Core.so.5
#5 0x00007f61ee9d0374 in start_thread () from /usr/lib/libpthread.so.0
#6 0x00007f61efe7627d in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7f61e33b5800 (LWP 3269)):
[KCrash Handler]
#6 0x00007f61efdc14b7 in raise () from /usr/lib/libc.so.6
#7 0x00007f61efdc288a in abort () from /usr/lib/libc.so.6
#8 0x00007f61f09eb8bf in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#9 0x00007f61f09e6bce in qt_assert(char const*, char const*, int) () from
/usr/lib/libQt5Core.so.5
#10 0x000000000042ac8f in main (argc=1, argv=0x7ffe7ba14b38) at
/home/vishesh/kde5/src/baloo_alt/src/file/main.cpp:76
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list