Summary: | Kdevelop reliably crashes when Project -> Open Configuration | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Roman Lebedev <lebedev.ri> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | 0xd34df00d, kfunk, mail |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.0.1 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=369324 | ||
Latest Commit: | http://commits.kde.org/kdevelop/35477927f7dba97fd178ac662c88af725521e3ce | Version Fixed In: | 5.0.2 |
Description
Roman Lebedev
2016-09-25 13:06:21 UTC
It shouldn't crash in any case, but to debug this problem: is cmake in your $PATH? Yes, it is. From https://bugs.kde.org/show_bug.cgi?id=369324#c1, which is the same issue as this one as now know: TLDR: Can't load plugin "KDevCMakeBuilder" some of its required dependencies could not be fulfilled: "org.kdevelop.IMakeBuilder" Precedes crash If i enable make and cmake plugins in kdevelop settings, the issue goes away. *** Bug 369324 has been marked as a duplicate of this bug. *** Ah, great, that's getting a lot closer to a solution. We should certainly fix the crash. The more on-track question is though, how did the make plugin get disabled? Did you turn it off by hand? Yes, i did disable it by hand. I think, i only disabled the 'make', not 'cmake' plugins. But why? @Kevin: We could fix that -- or maybe we should just not allow to disable those plugins? What's the point? Because, at the time, i thought that since i only use cmake-based projects, i do not need make plugin. For most plugins, KDevelop does lazy-loading anyways (i.e. only loads the plugin when needed) even if they are enabled. So there is little to no reason to ever disable a plugin, except e.g. if it crashes. Which means that, in my opinion, we should consider removing the option for the relevant plugins. Disabling a language might make sense, but why would anyone want to disable the Projects toolview plugin, VCS plugins, or project managers? Git commit 35477927f7dba97fd178ac662c88af725521e3ce by Sven Brauch. Committed on 15/10/2016 at 11:03. Pushed by brauch into branch '5.0'. CMake manager: correcly document dependency on KDevCMakeBuilder plugin in JSON file There's an assert or a crash if the plugin is not available at runtime. This happens if you disable the make and ninja plugins, or if they cannot be loaded for some reason. Related: bug 370836 M +4 -1 projectmanagers/cmake/kdevcmakemanager.json http://commits.kde.org/kdevelop/35477927f7dba97fd178ac662c88af725521e3ce Thank you! Git commit fb0230e3b6f08303ae92b1912268733d73348061 by Sven Brauch. Committed on 15/10/2016 at 11:17. Pushed by brauch into branch 'master'. more helpful error message when failing to load project plugin M +2 -1 shell/project.cpp http://commits.kde.org/kdevplatform/fb0230e3b6f08303ae92b1912268733d73348061 *** Bug 368826 has been marked as a duplicate of this bug. *** |