| Summary: | Crash during autocomplete under Wayland. | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | David Gow <david> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | admin, frmdstryr, mail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David Gow
2020-02-23 01:36:28 UTC
Looks like a Qt bug to me. Our application is not involved in the trace of the crashing frame at all. This crash occurs so frequently it makes KDevelop unusable for python code. I noticed two things: 1. It only seems to happen on python source code 2. After crashing and restarting it (the autocomplete) usually works one time 3. When it crashes it is showing two popup autocompletions at the same time Disabling "Enable auto completion" under the Settings -> Editing -> Auto Completion prevents this from crashing. But somehow autocomplete still works... could this be some issue with the python plugin? It's possible -- plugins can request completion to start when they think it makes sense, maybe that somehow interferes with the automatic invocation on Wayland. Unfortunately I have no wayland dev setup right now. I don't think this is python-specific: I was seeing it with C code. Please disregard the part about disabling "Enable auto completion", it still seems to occur either way, just less frequently. Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! (In reply to Justin Zobel from comment #6) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! I have not seen this lately. I also haven't noticed this recently, though I am now on a different setup that when I first reported it. Probably safe to close, and I'll reopen it if it recurs. 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 mark the bug 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! 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! |