Summary: | Crash running search query [liblmdb.so] | ||
---|---|---|---|
Product: | [Unmaintained] Baloo | Reporter: | Xavion <Xavion.0> |
Component: | General | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kde, pinak.ahuja, plasma-bugs, Xavion.0 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Backtrace for case 1 and/or 3 |
Description
Xavion
2015-11-13 21:28:54 UTC
Please add a backtrace. Created attachment 95503 [details]
Backtrace for case 1 and/or 3
I had a lot of trouble reproducing this bug today; whereas, it was flowing like a river yesterday. In this case, I was typing a bunch of random characters into the search field super quickly. Despite this, I don't know whether it crashed because of the speed or the character count.
Thanks! However - could you install debug symbols for baloo and liblmdb and crash again? The backtrace is enough to pinpoint those, but lacks detail information. I wouldn't have thought this is necessary, given that I've got "File Search" (Baloo) completely disabled. Actually, maybe this in itself is what's causing the problem. Do you think that could be the case, or do I still need to install those debug symbols? >do I still need to install those debug symbols? No it's fine. It's fixed in new updates. *** This bug has been marked as a duplicate of bug 349933 *** Whew, thank Christ for that! Whenever someone wants me to recompile a prebuilt package with debug symbols enabled, I start by commissioning a search for "more important" tasks that must be done first :-). |