SUMMARY I would like to ask You, if is it possible that a KDevelop package needs a rebuild after updating to last KDE frameworks? Since the system update last night I have the following problem: At least the VI mode and slider minimap KDevelop settings is broken and changing it in the setup is without any effect. I want to have the VI mode always enabled and the slider minimap always disabled, and I have this set in the KDevelop settings. But this setting is completely ignored and only the KDevelop context menu setting is taken in the account. Which is unfortunately the other behaviour in default (minimap enabled and VI mode disabled). The similar settings in KWrite works fine. STEPS TO REPRODUCE 1. Open KDevelop setting and ensure that the VI mode is still enabled and the slider minimap is disabled 2. Try in the editor, if the VI mode is really enabled 3. Observe, if the slider minimap is really turned off OBSERVED RESULT Settings of the VI mode is turned off, because of it is turned of in the context menu by default. Settings of the slider minimap is turned on because of it is turned on in the context menu by default EXPECTED RESULT VI mode shall be turned on and set as the default in the KDevelop context menu The slider minimap shall be turned off and set as the default in the context menu SOFTWARE/OS VERSIONS Linux/KDE Plasma: 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.14.2 ADDITIONAL INFORMATION journal -xe contains strange errors: kvě 11 12:26:42 iccmonb kdevelop[10065]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kvě 11 12:26:42 iccmonb kdevelop[10065]: kdevplatform.shell: Can't load plugin "kdevastyle" because a factory to load the plugin could not be obtained: "Knihovnu /usr/lib/qt/plugins/kdevplatform/33/kdevastyle.so nelze nahrát: (libastyle.so.3: sdílený objektový soubor ne> kvě 11 12:26:46 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a top-context from file "~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979" - the required language-support for handling ID 100 is probably not load> kvě 11 12:26:46 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a top-context from file "~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979" - the required language-support for handling ID 100 is probably not load> kvě 11 12:26:46 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a top-context from file "~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979" - the required language-support for handling ID 100 is probably not load> kvě 11 12:26:50 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a top-context from file "~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979" - the required language-support for handling ID 100 is probably not load> kvě 11 12:26:52 iccmonb kwin_x11[673]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58082, resource id: 117440523, major code: 18 (ChangeProperty), minor code: 0 kvě 11 12:26:52 iccmonb kdevelop[10065]: qrc:/qml/Develop.qml:139:21: QML Heading: Binding loop detected for property "font.pointSize" kvě 11 12:26:52 iccmonb kdevelop[10065]: qrc:/qml/area_code.qml:87:9: QML Heading: Binding loop detected for property "font.pointSize" kvě 11 12:26:52 iccmonb kdevelop[10065]: qrc:/qml/area_code.qml:63:9: QML Heading: Binding loop detected for property "font.pointSize" kvě 11 12:26:55 iccmonb kdevelop[10065]: kdevelop.plugins.welcomepage: "Last fetch of news feed was on po kvě 11 09:01:03 2020 GMT+0200" kvě 11 12:27:03 iccmonb kdevelop[10065]: kdevelop.plugins.python.duchain: Custom python interpreter "/usr/local/bin/python3.6dm" configured for project "IDP-pyqt" is invalid, using default kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objc++src" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objchdr" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objc++src" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objchdr" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objc++src" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objchdr" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objc++src" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objchdr" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objc++src" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin "kdevcustomscript" supports unknown mimetype entry "text/x-objchdr" kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevelop.plugins.customscript: indent returned empty text for style "GNU_indent_GNU" "indent" kvě 11 12:27:13 iccmonb kdevelop[10065]: kdevelop.plugins.customscript: indent returned empty text for style "GNU_indent_GNU" "indent" kvě 11 12:27:14 iccmonb kdevelop[10065]: kdevplatform.shell: Settings in config page Heaptrack::GlobalConfigPage(0x5643303d0e30, name = "Heaptrack__GlobalConfigPage") changed, while UiPreferences(0x56432fb6f3b0, name="UiConfig") is currently selected. This case is not i> kvě 11 12:27:14 iccmonb kdevelop[10065]: kdevplatform.shell: Settings in config page cppcheck::GlobalConfigPage(0x5643303c9bc0, name = "cppcheck__GlobalConfigPage") changed, while UiPreferences(0x56432fb6f3b0, name="UiConfig") is currently selected. This case is not imp> kvě 11 12:27:14 iccmonb kdevelop[10065]: kdevplatform.shell: Settings in config page ClangTidyPreferences(0x564330418c40, name = "ClangTidyPreferences") changed, while UiPreferences(0x56432fb6f3b0, name="UiConfig") is currently selected. This case is not implemented yet. kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 498 504 0 kvě 11 12:27:25 iccmonb kdevelop[10065]: kdevplatform.language: invalid item for index 474 504 0 ...
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 ***