| Summary: | KDevelop Crashes No Action after kdev-python plugin installed | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | chris+kdebug |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | chris+kdebug, mail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
chris+kdebug
2019-06-20 21:36:11 UTC
Created attachment 121045 [details]
New crash information added by DrKonqi
kdevelop (5.2.1) using Qt 5.9.5
- What I was doing when the application crashed:
Typing and actually coding in the application.
- Custom settings of the application:
Crashes began after installing the kdev-python plugin from the Ubuntu Repos (Dist bionic 16.04).
-- Backtrace (Reduced):
#6 0x00007f1e01d7b0af in () at /usr/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#7 0x00007f1e01d5eefd in Python::ContextBuilder::visitLambda(Python::LambdaAst*) () at /usr/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#8 0x00007f1e1abbce2c in Python::AstDefaultVisitor::visitClassDefinition(Python::ClassDefinitionAst*) () at /usr/lib/x86_64-linux-gnu/libkdevpythonparser.so
#9 0x00007f1e01d5d1b8 in Python::ContextBuilder::visitClassDefinition(Python::ClassDefinitionAst*) () at /usr/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#10 0x00007f1e1abbc12c in Python::AstDefaultVisitor::visitCode(Python::CodeAst*) () at /usr/lib/x86_64-linux-gnu/libkdevpythonparser.so
Disabling the kdev-python plugin in the interface seems to fix the problem. Sorry I didn't see this earlier [technically it should be filed under 'kdev-python' rather than 'kdevelop' but I know the bug filing system sucks for users]. This appears to be the same as a previously-reported bug that was fixed in 5.2.2. See the linked issue for more details. Thanks for the report! *** This bug has been marked as a duplicate of bug 389326 *** |