Application: konqueror (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.6.13-1-MANJARO-RPI4 aarch64 Windowing System: X11 Distribution: Manjaro ARM DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Konqueror/Kate crashes upon selection of "vi mode" as soon as I select the X button. The crash can be reproduced sometimes. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault [KCrash Handler] #4 0x0000fffefb39ca54 in () at /usr/lib/libKF5TextEditor.so.5 #5 0x0000ffff888c897c in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #6 0x0000ffff894d543c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #7 0x0000ffff88892540 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #8 0x0000ffff88896038 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #9 0x0000ffff888ffb80 in () at /usr/lib/libQt5Core.so.5 #10 0x0000ffff85a76e70 in () at /usr/lib/libglib-2.0.so.0 #11 0x0000ffff85a796f8 in () at /usr/lib/libglib-2.0.so.0 #12 0x0000ffff85a79fb4 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #13 0x0000ffff888fef28 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #14 0x0000ffff88890704 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #15 0x0000ffff8889ae9c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #16 0x0000ffff8afa7ca4 in () at /usr/lib/libkdeinit5_konqueror.so #17 0x0000ffff8afa8228 in () at /usr/lib/libkdeinit5_konqueror.so #18 0x0000ffff8b0585b8 in kdemain () at /usr/lib/libkdeinit5_konqueror.so #19 0x0000ffff8adb7b80 in () at /usr/lib/libc.so.6 #20 0x0000ffff8adb7c60 in __libc_start_main () at /usr/lib/libc.so.6 #21 0x0000aaaab6e106f0 in () [Inferior 1 (process 938) detached] Reported using DrKonqi
I can't reproduce this bug using Frameworks 5.115.0. Just to be clear, when you say "I select the X button", which button are you referring to? The x key on the keyboard, the X button on the title bar which closes the window, or something else?
As soon as I select Esc and enter q! in vi mode...it crashes. > On 03/05/2024 12:46 PM MST Stefano Crocco <bugzilla_noreply@kde.org> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=482436 > > Stefano Crocco <stefano.crocco@alice.it> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |stefano.crocco@alice.it > > --- Comment #1 from Stefano Crocco <stefano.crocco@alice.it> --- > I can't reproduce this bug using Frameworks 5.115.0. Just to be clear, when you > say "I select the X button", which button are you referring to? The x key on > the keyboard, the X button on the title bar which closes the window, or > something else? > > -- > You are receiving this mail because: > You reported the bug.
(In reply to iwm from comment #2) > As soon as I select Esc and enter q! in vi mode...it crashes. Ok, now I can reproduce it. I'll investigate it as soon as I have time
Thank you...very annoying. > On 03/06/2024 1:45 PM MST Stefano Crocco <bugzilla_noreply@kde.org> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=482436 > > Stefano Crocco <stefano.crocco@alice.it> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #3 from Stefano Crocco <stefano.crocco@alice.it> --- > (In reply to iwm from comment #2) > > As soon as I select Esc and enter q! in vi mode...it crashes. > > Ok, now I can reproduce it. I'll investigate it as soon as I have time > > -- > You are receiving this mail because: > You reported the bug.
Here's a more complete backtrace (for Konqueror 24.02 and KTextEditor 6.0.0): #0 KateVi::AppCommands::closeCurrentDocument() at /usr/src/debug/kde-frameworks/ktexteditor-6.0.0/ktexteditor-6.0.0/src/vimode/appcommands.cpp:302 #1 QObject::event() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1.437 #2 QApplicationPrivate::notify_helper() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3.296 #3 QCoreApplication::notifyInternal2() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1.121 #4 QCoreApplication::sendEvent() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1.539 #5 QCoreApplicationPrivate::sendPostedEvents() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1.901 #6 QCoreApplication::sendPostedEvents() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1.760 #7 postEventSourceDispatch() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:243 #8 g_main_dispatch() at /usr/lib64/libglib-2.0.so.0 #9 g_main_context_iterate_unlocked.isra() at /usr/lib64/libglib-2.0.so.0 #10 g_main_context_iteration() at /usr/lib64/libglib-2.0.so.0 #11 QEventDispatcherGlib::processEvents() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #12 QEventLoop::exec() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:34 #13 QCoreApplication::exec() at /var/tmp/portage/dev-qt/qtbase-6.6.2/work/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #14 KonquerorApplication::startFirstInstance() at /home/stefano/documenti/programmi/konqueror-development/konqueror/src/konqapplication.cpp:272 #15 KonquerorApplication::start() at /home/stefano/documenti/programmi/konqueror-development/konqueror/src/konqapplication.cpp:335 #16 main() at /home/stefano/documenti/programmi/konqueror-development/konqueror/src/konqmain.cpp:18 As far as I can tell, the crash happens inside KTextEditor, because it tries to access the active view without checking whether it's valid or not. Here, the view is invalid and so the program crashes. I don't know whether this is caused by Konqueror doing something wrong with the Kate part or whether the bug is caused by the part itself. I'll try asking the part's developers for more informations.
The crash has been fixed in version 6.1 of the KDE Frameworks, but I don't know if the fix will be ported back to version 5. In any case, the fix they applied make the :q command do nothing in Konqueror, rather than closing the view as one could expect. Is this acceptable to you?
":q command do nothing in Konqueror, rather than closing the view as one could expect. Is this acceptable to you?" I would rather see the view closed...if possible. > On 04/21/2024 10:55 AM MDT Stefano Crocco <bugzilla_noreply@kde.org> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=482436 > > --- Comment #6 from Stefano Crocco <stefano.crocco@alice.it> --- > The crash has been fixed in version 6.1 of the KDE Frameworks, but I don't know > if the fix will be ported back to version 5. In any case, the fix they applied > make the :q command do nothing in Konqueror, rather than closing the view as > one could expect. Is this acceptable to you? > > -- > You are receiving this mail because: > You reported the bug. <pre>Sent by: Wm Loftin - iWm@wglware.com</pre>