Summary: | Broken settings agains the context menu after update to last KDE frameworks | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Martin Ottmar <mirovski36> |
Component: | UI: general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kossebau |
Priority: | NOR | ||
Version: | 5.5.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin Ottmar
2020-05-11 10:39:09 UTC
Huh. Looking to the file /var/log/pacman.log: [2020-05-08T01:33:57+0200] [ALPM] upgraded kdevelop (5.5.0-2 -> 5.5.1-1) I'm sorry, I have missed the last KDevelop update. So, it is possible that the problem mentioned above may be related to the KDevelop update, not to the following KDE frameworks update. My laptop and KDevelop was not (probably) restarted (at least) since thursday until today. There is chance something in KF 5.70 broke things here. Yet to be more investigated. See https://phabricator.kde.org/D27844#670942 I'm sorry. I've forgotten to fill status update. I saw few crashes of KDevelop last days (introduced maybe in KDevelop-5.5.0?). I didn't try to reproduce such crash yet, but it seems that it is related to LMB probably with a mouse dragging (maybe after switching applications?). I noticed that probably each of these crashes leads to partial loss of KDevelop configuration. All opened files and projects, but even enabled module settings is forgotten after this crash. I spotted the last crash just yesterday. After re-configuration, I noticed that the behaviour mentioned in this bugreport is gone. What is interesting, I didn't need to change the other settings, only the modules setting was forgotten, it seems. And since the last crash, the VI mode works correctly, and vertical slider minimap is turned off, both as it is set in my KDevelop settings. So it is possible, that this problem can be solved simply by deleting old configuration files. So, maybe this bug should be closed. Thanks for your last update. While you saw some things fixed when it comes to view settings, like slider minimap, I very much expect by what I know meanwhile you will see them again once you closed and reopened a kdevelop session. As this has turned out to be indeed a bug due to the config session storage issue I linked to, and which meanwhile got a reverted commit with a respective KF KTextEditor module patch release, 5.70.1, currently pushed out. For any crashes, please report them separately as new bugs if you still encounter them. As you asked initially: In general does kdevelop not need a recompilation if KF or Qt has a new version, kdevelop itself only uses the stable public API of those libraries, so those libraries can be upgraded without a need to rebuild kdevelop. So this was not the issue here, and for the given reason also it not expected to be one for others. *** This bug has been marked as a duplicate of bug 421375 *** |