Summary: | Crash when select several files | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Baloo | Reporter: | blackredprince |
Component: | General | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bugs, emmanuelpescosta099, fademind, frank78ac, hh.kde.crash, karl, ruanbeihong, silvio.frischi |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.15 | |
Attachments: | valgrind log of crash |
Description
blackredprince
2015-09-06 21:19:24 UTC
Thanks for the bug report. Could you please provide a backtrace of the crash (and, if possible, also a Valgrind log) and your Dolphin version? See https://community.kde.org/Dolphin/FAQ/Crashes Thanks for your help. Created attachment 94462 [details]
valgrind log of crash
Dolphin help: Version 15.08.0 Using: KDE Frameworks 5.14.0 Qt 5.4.1 (built against 5.4.1) The xcb windowing system Sorry, but there is no another baktrace or logs available for dolphin I used to have this problem too. same backtrace Version 15.08.0 Using: KDE Frameworks 5.14.0 Qt 5.4.2 (built against 5.4.2) The xcb windowing system then I pushed System Settings -> Search -> Plasma Search -> Clear History and now I can't reproduce it anymore. Update kde to 5.4.1. All the same. Clear history, but this didnt help I also turned on and off again "enable File Search" in the next tab. I wasn't sure which of the two did the trick so I wrote the one that I thought more likely. In anycase, the second last function in backtrace was something with baloo, which has something to do with searching, so playing around with those options a bit might get it running again. Silvio, I repeat your steps - turn on and turn off search. then clear history and all works fine now. Thanx, but bug still exist somewhere ) I agree. The bug is still there. Probably caused by upgrading (Ubuntu 15.04 to 15.10) with File Search disabled (if anyone wants to try to reproduce it). I'm just a user like you, so it's not up to me. Thanks for the Valgrind log. Looks like a Baloo issue. ==5686== Warning: set address range perms: large range [0x3a056000, 0x17a056000) (defined) ==5686== Invalid read of size 4 ==5686== at 0x11AC5960: mdb_txn_begin (in /usr/lib/x86_64-linux-gnu/liblmdb.so.0.0.0) ==5686== by 0x7B53854: Baloo::File::load() (in /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5.14.0) ==5686== by 0x75D64C0: ??? (in /usr/lib/x86_64-linux-gnu/libKF5BalooWidgets.so.5.0.0) ==5686== by 0xA4AF739: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0x9703B2B: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.1) ==5686== by 0x9708FFF: QApplication::notify(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.1) ==5686== by 0xA47DC2A: QCoreApplication::notifyInternal(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0xA47FC9A: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0xA4D6842: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0xE636C3C: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.1) ==5686== by 0xE636F1F: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.1) ==5686== by 0xE636FCB: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.1) ==5686== Address 0xc is not stack'd, malloc'd or (recently) free'd ==5686== ==5686== ==5686== Process terminating with default action of signal 11 (SIGSEGV) ==5686== Access not within mapped region at address 0xC ==5686== at 0x11AC5960: mdb_txn_begin (in /usr/lib/x86_64-linux-gnu/liblmdb.so.0.0.0) ==5686== by 0x7B53854: Baloo::File::load() (in /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5.14.0) ==5686== by 0x75D64C0: ??? (in /usr/lib/x86_64-linux-gnu/libKF5BalooWidgets.so.5.0.0) ==5686== by 0xA4AF739: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0x9703B2B: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.1) ==5686== by 0x9708FFF: QApplication::notify(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.1) ==5686== by 0xA47DC2A: QCoreApplication::notifyInternal(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0xA47FC9A: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0xA4D6842: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.1) ==5686== by 0xE636C3C: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.1) ==5686== by 0xE636F1F: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.1) ==5686== by 0xE636FCB: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.1) *** Bug 352686 has been marked as a duplicate of this bug. *** *** Bug 353086 has been marked as a duplicate of this bug. *** *** Bug 353209 has been marked as a duplicate of this bug. *** I had similar situation like this. Dolphin opened and flashed and then automatically closed. When I try to debug that, also a SIGSEGV. And Valgrind trace back to Baloo::File::load() and finally mdb_txn_begin of liblmdb. I found that I didn't have baloo-kf5 installed in my system. Then I installed it. Nothing changed. Then I clean the search just as Silvio Frischknecht said: "System Settings -> Search -> Plasma Search -> Clear History" and it vanished as the same. |