Summary: | Krunner crashes on start of typing / directly after calling it | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | Stefan Krüger <mail> |
Component: | general | Assignee: | Kai Uwe Broulik <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.7.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Stefan Krüger
2017-05-10 14:33:08 UTC
Duplicate of https://bugs.kde.org/show_bug.cgi?id=378493 *** This bug has been marked as a duplicate of bug 378493 *** Not a duplicate, the backtraces are not related. If this is reproducible, a valgrind log would help to debug this memory corruption. @(In reply to Christoph Feck from comment #2) i have update my system to 17.04 some time ago. currently i can not reproduce this behavior. so eventually we could just close this? if it helps - i think i have a backup image/disc of the old system some where - i could try to put it back in and check if i can reproduce it then. do you have a good tutorial / getting-started information on valgrind logs? (i currently don't know what it is / how to perform this kind of logs..) That's good, it's probably fixed now. A lot of KRunner crashing bugs have been fixed since Ubuntu 16.10 was packaged. |