| Summary: | konsole crashes while typing inside nano editor | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | orionbelt2 |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | cfeck, orionbelt2 |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 16.04.1 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Backtrace of konsole segmentation fault | ||
|
Description
orionbelt2
2016-06-21 22:28:15 UTC
I am adding that i updated konsole to version 16.04.1 and the bug is still there. Please try Qt 5.6.1. According to the backtrace, the bug is in Qt's xcb platform plugin. If this is still reproducible with newer Qt version, please report this error to https://bugreports.qt.io/ Thanks for the feedback, Christoph. I attempted to update to dev-qt/qtcore-5.6.1 on Gentoo, but the system wants me to basically upgrade many/all of my Qt packages... Unfortunately i cannot do this right now, it is a major upgrade to potentially unstable packages, and this is my work machine... I'll have to wait until Gentoo makes this (or higher) the stable version... What i did instead: I upgraded x11-libs/libxcb and x11-proto/xcb-proto to 1.12 so that if, by any chance, it is actually an issue with XCB itself, it may be fixed. Konsole hasn't crashed so far, but i haven't been using it for too long since restarting KDE. I'll put up another report here either way, whether it crashes or it keeps working for some time. Unfortunately, upgrading x11-libs/libxcb and x11-proto/xcb-proto to 1.12 did not help... OK, so i was able to come up with an easy way to upgrade all my Qt packages, including dev-qt/qtcore which is now at version 5.6.1. Unfortunately, the bug is still there: After some time of intensive typing and keyboard layout switching in nano, called by mutt, the entire konsole crashes. Please let me know if there something else that i could do to help with the debugging. This is a very serious problem. Does your distribution also offer debug symbol packages for Qt? Before it makes sense to report it to Qt developers, I would like to see an updated backtrace with debug symbol information. Gentoo Linux builds from source, so it does not provide debug symbol packages but allows people to build packages that provide debug symbols: https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces I skimmed through the text, and although it does not sound complicated, there are still a few things i have to figure out since i have not done it before... Unfortunately, i do not have the time to do this right now, it will have to wait for a week or more... In the weeks after i filed this bug, its frequency got reduced from a few times per day to a few times per week, and i found a way to preserve my work in between crashes, so the bug became less debilitating. However, after many months of no further improvement, the bug became again sufficiently annoying that i set up backtraces on all my dev-qt/* packages. The konsole crashed again, and here i am submitting a backtrace (see attachment). I hope this backtrace is more useful than my previous one. Thanks! Created attachment 104797 [details]
Backtrace of konsole segmentation fault
The backtrace is much better, and reveals the cause of the crash: QComposeInputContext::commitText() tries to send an event to a NULL object. Please report this issue to Qt developers. Thanks for the prompt feedback. Well, i do not have an account on Qt's bug report system, and i think KDE devs often contribute bug reports there, so is there a way that you or someone else might want to do it? If not, i guess i'll have to bite the bullet... I cannot reproduce the bug, so I will not report it. If Qt developers need more information, only someone who can reproduce the bug will be able to provide it. Checking available input method plugins in Qt, there is also "ibus" besides "compose", so you might check if switching to IBus helps to resolve the issue. On the other hand, we always had many crashes with input method helpers; it seems they are not used by many people. |