Bug 459189 - KWrite crashes when 3-finger-tap on the text area
Summary: KWrite crashes when 3-finger-tap on the text area
Status: RESOLVED UPSTREAM
Alias: None
Product: kate
Classification: Applications
Component: kwrite (show other bugs)
Version: 22.04.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-09-15 21:52 UTC by Toby
Modified: 2022-11-19 18:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toby 2022-09-15 21:52:29 UTC
Application: kwrite (22.04.1)

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.19.8-200.fc36.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
As the title says, KWrite crashes every time I do a 3-finger-tap on the text area.

The crash can be reproduced every time.

-- Backtrace:
Application: KWrite (kwrite), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f2135abd259 in QtWaylandClient::QWaylandInputDevice::Touch::touch_frame() () from /lib64/libQt5WaylandClient.so.5
#5  0x00007f2133399746 in ffi_call_unix64 () from /lib64/libffi.so.8
#6  0x00007f21333964d2 in ffi_call_int.lto_priv () from /lib64/libffi.so.8
#7  0x00007f2135a2fe03 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0
#8  0x00007f2135a30573 in dispatch_event.isra () from /lib64/libwayland-client.so.0
#9  0x00007f2135a3073c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0
#10 0x00007f2135ab9615 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#11 0x00007f21381572b4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#12 0x00007f2138be8d22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#13 0x00007f213812d218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007f2138130584 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x00007f213817e457 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#16 0x00007f2135e16faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007f2135e6c2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#18 0x00007f2135e14940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007f213817df4a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007f213812bc6a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007f2138133d32 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#22 0x0000563557a7ff05 in main ()
[Inferior 1 (process 2773) detached]

Reported using DrKonqi
Comment 1 Christoph Cullmann 2022-11-19 18:31:14 UTC
Hi, the backtrace rather points to some issue inside Qt or the Wayland stack.
Please consider to report that upstream there.