[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #34 from doc.ev...@gmail.com --- (In reply to Christoph Cullmann from comment #33) > Yes, thanks. If that only is triggered there, I am not sure that is really a > KTextEditor issue. I have no idea where the issue lies. Since I'm just an ordinary person trying to get some work done on my debian stable systems, all I can do really is report the bug and send stack traces, which is what I've done. My original report is https://bugs.kde.org/show_bug.cgi?id=473251. I think that I'll just go back to using codeview; I'm spending too long waiting waiting for kdevelop to recover after each crash; it's just too frustrating to try to use something that's so unstable :-( The main project that I'm working on, https://github.com/N7DR/drlog, is big enough that even just starting kdevelop with that project takes more than a minute on my development machine. Waiting all that time after each kdevelop crash really is getting to be just too frustrating :-( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #33 from Christoph Cullmann --- (In reply to doc.evans from comment #32) > (In reply to Christoph Cullmann from comment #31) > > Hi, just to be sure: That happens for Kate, too? > > If that question is intended for me, the answer is that, per comment #20, > the only program in which I've experienced a crash is kdevelop. Yes, thanks. If that only is triggered there, I am not sure that is really a KTextEditor issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #32 from doc.ev...@gmail.com --- (In reply to Christoph Cullmann from comment #31) > Hi, just to be sure: That happens for Kate, too? If that question is intended for me, the answer is that, per comment #20, the only program in which I've experienced a crash is kdevelop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #31 from Christoph Cullmann --- Hi, just to be sure: That happens for Kate, too? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #30 from doc.ev...@gmail.com --- (In reply to Igor Kushnir from comment #28) > (In reply to doc.evans from comment #26) > > So I am quite puzzled by the above. I obviously have KDE installed, > > otherwise I could not be using kdevelop. But I'm not actually running KDE as > > a desktop environment on either of the machines here that exhibit the > > problem. So is there some KDE-related config file somewhere that I should > > edit in order to be sure that accessibility support is turned off when I run > > kdevelop? > The commit adds at option to turn accessibility off into the > Editor=>Editing=>General page of the Configure KDevelop dialog. However the > commit wasn't cherry picked into the kf5 branch. So it will become available > in KDevelop only once it is ported to KF6. If someone can confirm that > patching a KF5 version of KTextEditor with the commit and turning > accessibility off eliminates this crash, then maybe we could cherry-pick it > into the kf5 branch of KTextEditor. I have no way to test anything... just an ordinary user... but I got hit with this five times in less than an hour a couple of days ago when I was trying to tidy up some code, so am seriously thinking of going back to codelite (which certainly has problems of its own, which is why I left it in favour of kdevelop, but at least it doesn't crash), just because this bug is so frustrating and keeps getting in the way of the task at hand -- it feels like driving a car that stalls every few miles :-( -- yes, you can get the job done, but you waste an awful lot of time trying to get the car restarted (or recovering from the kdevelop crash). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Christoph Cullmann changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #29 from Christoph Cullmann --- One can turn it off in master and for any more changes we would need a way to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added Ever confirmed|0 |1 CC||igor...@gmail.com Status|REPORTED|CONFIRMED --- Comment #28 from Igor Kushnir --- (In reply to doc.evans from comment #26) > So I am quite puzzled by the above. I obviously have KDE installed, > otherwise I could not be using kdevelop. But I'm not actually running KDE as > a desktop environment on either of the machines here that exhibit the > problem. So is there some KDE-related config file somewhere that I should > edit in order to be sure that accessibility support is turned off when I run > kdevelop? The commit adds at option to turn accessibility off into the Editor=>Editing=>General page of the Configure KDevelop dialog. However the commit wasn't cherry picked into the kf5 branch. So it will become available in KDevelop only once it is ported to KF6. If someone can confirm that patching a KF5 version of KTextEditor with the commit and turning accessibility off eliminates this crash, then maybe we could cherry-pick it into the kf5 branch of KTextEditor. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||deb...@gruz.net --- Comment #27 from Igor Kushnir --- *** Bug 475924 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #26 from doc.ev...@gmail.com --- (In reply to Waqar Ahmed from comment #25) > > Allow enabling/disabling accessibility > > On Manjaro KDE (and possibly others) it seems that accessibility is > always enabled for some reason. Lately it has been causing a lot of > crashes in KDevelop and in general it is really bad for performance So I am quite puzzled by the above. I obviously have KDE installed, otherwise I could not be using kdevelop. But I'm not actually running KDE as a desktop environment on either of the machines here that exhibit the problem. So is there some KDE-related config file somewhere that I should edit in order to be sure that accessibility support is turned off when I run kdevelop? (FWIW, on one machine I simply ssh into the machine and run kdevelop over the network, so there is no desktop environment at all; on the other machine I am using Trinity as the desktop environment.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #25 from Waqar Ahmed --- Git commit a64125ae585c96ee16081fc75d525624311001cc by Waqar Ahmed. Committed on 19/10/2023 at 18:31. Pushed by cullmann into branch 'master'. Allow enabling/disabling accessibility On Manjaro KDE (and possibly others) it seems that accessibility is always enabled for some reason. Lately it has been causing a lot of crashes in KDevelop and in general it is really bad for performance especially if you are doing something that results in a large number of edits at once M +17 -0src/dialogs/editconfigwidget.ui M +3-0src/dialogs/katedialogs.cpp M +1-0src/utils/kateconfig.cpp M +1-0src/utils/kateconfig.h M +2-0src/view/kateview.cpp M +1-0src/view/kateview.h M +3-3src/view/kateviewinternal.cpp https://invent.kde.org/frameworks/ktexteditor/-/commit/a64125ae585c96ee16081fc75d525624311001cc -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #24 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/617 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Bug Janitor Service changed: What|Removed |Added Priority|HI |VHI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||rob...@robertoldham.com --- Comment #23 from Igor Kushnir --- *** Bug 475766 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #22 from doc.ev...@gmail.com --- (In reply to doc.evans from comment #21) > When I reported this bug (as https://bugs.kde.org/show_bug.cgi?id=472891) I > was using the nouveau driver on the X server. Using that driver, the crashes > were frequent. > > Last week I switched to the modesetting driver (details in this thread: > https://lists.debian.org/debian-user/2023/09/msg00218.html) on the machine > on which the X server resides. Since then, this crash has not occurred, > despite considerable use of kdevelop. > > No other relevant changes that I know of were made. I spoke too soon. I am still seeing crashes. I get the distinct impression that they are less frequent, but perhaps that's just wishful thinking. It was certainly true for a while after changing drivers, but I could believe that that was just random happenstance. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #21 from doc.ev...@gmail.com --- When I reported this bug (as https://bugs.kde.org/show_bug.cgi?id=472891) I was using the nouveau driver on the X server. Using that driver, the crashes were frequent. Last week I switched to the modesetting driver (details in this thread: https://lists.debian.org/debian-user/2023/09/msg00218.html) on the machine on which the X server resides. Since then, this crash has not occurred, despite considerable use of kdevelop. No other relevant changes that I know of were made. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #20 from doc.ev...@gmail.com --- Just to confirm that this isn't associated with Wayland. I reported bug https://bugs.kde.org/show_bug.cgi?id=473251 which is perhaps the same bug (although I'm not absolutely certain about that) and I don't use Wayland at all. In fact here it's always X-over-ssh. In case it helps, here is part of my most recent post on bug 473251: 2. The crashes occur at the rate of about two per hour... I can get work done, but it's certainly annoying to be interrupted by crashes so frequently. 3. I have not found a particular sequence of actions that is guaranteed to reproduce the crash. 4. I *think* that crashes happen only when I've actively interacted with the editor window: either I'm in the middle of typing, or at the very least, I've just clicked somewhere in the window. 5. FYI, the project I'm working on is: https://github.com/N7DR/drlog. Since installing debian bookworm on the computer in question, I have never seen any crash except when using kdevelop (i.e., not when using Kate or any other KDE program). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #19 from Igor Kushnir --- *** Bug 473250 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #18 from Waqar Ahmed --- Since we haven't gotten even a single bugreport from Kate users I am inclined to believe that this might be a bug in KDevelop -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||doc.ev...@gmail.com --- Comment #17 from Igor Kushnir --- *** Bug 472891 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #16 from Igor Kushnir --- *** Bug 453773 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||ad...@xutaxkamay.com --- Comment #15 from Igor Kushnir --- *** Bug 453684 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #14 from Igor Kushnir --- *** Bug 449294 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||gmranda...@gmail.com --- Comment #13 from Igor Kushnir --- *** Bug 448885 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||thijs.with...@gmail.com --- Comment #12 from Igor Kushnir --- *** Bug 446487 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Igor Kushnir changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #11 from Igor Kushnir --- *** Bug 462455 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #10 from Martin Ottmar --- Still keeps crashing "randomly". Few minutes ago just after pressing Alt+TAB to get into KDevelop followed by pressing key "Key_Down" (immediatelly) in order to see lower lines in the current editor tab with some python code. It is possible that the Ctrl key has been pressed too at the same time (HP laptop with some bios troubles in linux - it generates Ctrl key press randomly, especially under heavy load - not spotted in MS Windows when analysed by our technicians). It has been the first crash in QAccessibleEvent related to a key press. Usually, it crashes just after LMB on an editor tab or inside the editor window, but I think, always just after applications switch. Updated Archlinux (5.98.0, 22.08.1), KDevelop with VI mode and with the kdev-python plugin from AUR. Normal X-server configuration with plasma, no any wayland. Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f169e715f90 in QAccessibleObject::object() const () at /usr/lib/libQt5Gui.so.5 #5 0x7f169f1c00de in QAccessibleWidget::isValid() const () at /usr/lib/libQt5Widgets.so.5 #6 0x7f169e71f0fd in QAccessibleEvent::accessibleInterface() const () at /usr/lib/libQt5Gui.so.5 #7 0x7f169e71acb5 in QAccessible::updateAccessibility(QAccessibleEvent*) () at /usr/lib/libQt5Gui.so.5 #8 0x7f169bde0614 in KateViewInternal::cursorMoved() () at /usr/lib/libKF5TextEditor.so.5 #9 0x7f169bdd6bff in KateViewInternal::updateCursor(KTextEditor::Cursor, bool, bool, bool) () at /usr/lib/libKF5TextEditor.so.5 #10 0x7f169be50cdd in KateVi::NormalViMode::handleKeypress(QKeyEvent const*) () at /usr/lib/libKF5TextEditor.so.5 #11 0x7f169be6169c in KateVi::InputModeManager::handleKeypress(QKeyEvent const*) () at /usr/lib/libKF5TextEditor.so.5 #12 0x7f169be3e88a in KateViInputMode::keyPress(QKeyEvent*) () at /usr/lib/libKF5TextEditor.so.5 #13 0x7f169be3b8f7 in KateViInputMode::stealKey(QKeyEvent*) () at /usr/lib/libKF5TextEditor.so.5 #14 0x7f169bde2875 in KateViewInternal::eventFilter(QObject*, QEvent*) () at /usr/lib/libKF5TextEditor.so.5 #15 0x7f169e28c7f2 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f169ef78b0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f169ef7ddf8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f169e28cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f169efcf18b in () at /usr/lib/libQt5Widgets.so.5 #20 0x7f169ef78b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f169e28cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #22 0x7f169e73fb50 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5 #23 0x7f169e720dfe in bool QWindowSystemInterfacePrivate::handleWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #24 0x7f169e72a0e6 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /usr/lib/libQt5Gui.so.5 #25 0x7f169e73faf2 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5 #26 0x7f169e728985 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #27 0x7f167ff2f6c0 in () at /usr/lib/libQt5XcbQpa.so.5 #28 0x7f169a1e281b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #29 0x7f169a238ec9 in () at /usr/lib/libglib-2.0.so.0 #30 0x7f169a1e10d2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #31 0x7f169e2d750c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f169e28532c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7f169e28fe59 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #34 0x558bfb28cba9 in () #35 0x7f169da3c290 in () at /usr/lib/libc.so.6 #36 0x7f169da3c34a in __libc_start_main () at /usr/lib/libc.so.6 #37 0x558bfb28d715 in () [Inferior 1 (process 3769) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #9 from Ahmad Samir --- I was wrong, somehow the compiler casts it to the appropriate type; I was confused by the in the backtrace, but that could be gdb confused too by too many layers of inheritance/casts. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #8 from Christoph Cullmann --- I can't reproduce this myself. I fail to see how the change can work, given in all other locations we don't use the ->textInterface() call either, or are they all wrong? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740
Ahmad Samir changed:
What|Removed |Added
CC||a.samir...@gmail.com
--- Comment #7 from Ahmad Samir ---
I noticed this in the backtrace:
#3 0x7f4bde872db7 in KateViewInternal::cursorMoved() (this=0x563c189c63c0)
at /home/xaver/kde/src/ktexteditor/src/view/kateviewinternal.cpp:4114
ev =
"incomplete type" is a bit weird; looking at ktexteditor:
void KateViewInternal::cursorMoved()
{
view()->updateRangesIn(KTextEditor::Attribute::ActivateCaretIn);
#ifndef QT_NO_ACCESSIBILITY
if (QAccessible::isActive()) {
QAccessibleTextCursorEvent ev(this, static_cast(QAccessible::queryAccessibleInterface(this))->positionFromCursor(this,
m_cursor));
QAccessible::updateAccessibility();
}
#endif
}
QAccessible::queryAccessibleInterface() returns a QAccessibleInterface*, so
we'd have to use QAccessibleInterface::textInterface() to get a
QAccessibleTextInterface*; not sure if this makes a difference but I'd try:
@@ -4597,7 +4597,8 @@ void KateViewInternal::cursorMoved()
#ifndef QT_NO_ACCESSIBILITY
if (QAccessible::isActive()) {
-QAccessibleTextCursorEvent ev(this, static_cast(QAccessible::queryAccessibleInterface(this))->positionFromCursor(this,
m_cursor));
+KateViewAccessible *iface = static_cast(QAccessible::queryAccessibleInterface(this)->textInterface());
+QAccessibleTextCursorEvent ev(this, iface->positionFromCursor(this,
m_cursor));
QAccessible::updateAccessibility();
}
#endif
(If it works, feel free to use it in a MR).
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #6 from Waqar Ahmed --- Did some digging, but didn't get anywhere. Maybe the accessibleInterface pointer inside updateAccessibility() is invalid which leads to a crash. When we reload the doc, the views, if any are valid before and after regardless of whether they became visible or not. A quick workaround fix would be to allow the user to disable/enable accessibility. This would avoid the crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #5 from Zamundaaa --- I've seen it crashing with a similar backtrace on X11 myself as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #4 from Sven Brauch --- The other bug https://bugs.kde.org/show_bug.cgi?id=451041 says X11... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #3 from Waqar Ahmed --- Has it ever crashed in X? Maybe this is something specific to wayland, and it could be that kate users are just lucky till now -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #2 from Sven Brauch --- Hm, since you're not seeing it, it is of course possible it's specific to KDevelop. But in this trace, the KDevelop stacktrace looks innocent enough to me... the git plugin detected changes in this document, so it is being reloaded, and from the reload on everything is in KTextEditor only. Maybe some special condition is needed to trigger this, I could e.g. imagine something like "a document is being reloaded for which the view has never been visible before"? Unfortunately I have absolute zero knowledge about QAccessible :/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Waqar Ahmed changed: What|Removed |Added CC||mirovsk...@gmail.com --- Comment #1 from Waqar Ahmed --- *** Bug 451041 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
