Summary: | Infinite loop in sqlite3BtreeCursor | ||
---|---|---|---|
Product: | [Plasma] kactivitymanagerd | Reporter: | Peter Cordes <peter> |
Component: | general | Assignee: | Ivan Čukić <ivan.cukic> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | plasma-bugs |
Priority: | NOR | Keywords: | triaged |
Version: | 5.11.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Peter Cordes
2018-01-27 05:32:35 UTC
This is the most interesting report I've seen in a while. Can you try to reproduce this with the debugging symbols enabled so that I can at least see which query is a culprit? I'm afraid the issue is in the sqlite library itself or in Qt (since kamd uses Qt's SQL framework - no direct sqlite calls are performed). If you can provide the information requested in comment #1, please add it. To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. I don't know what triggered this bug in the first place, and I only saw it that one time, sorry. I really wish Arch had a way to grab debug symbols for binaries you're already running, because building new packages won't necessarily have the same addresses. Otherwise I could have done something more useful with the original crash. I don't do anything with KDE "activities", other than accidentally hit super+tab and bring up the switcher. I tried some stuff, including running kactivities-cli --list-activities, to poke at kactivitymanagerd a tiny but, but it didn't repro this bug. I think we're just going to have to wait for someone to stumble onto this bug again, and hopefully find this report. :( Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |