Bug 442091

Summary:	(Wayland) Plasma crashes when trying to move window with S Pen (Samsung Notebook 9 Pro)
Product:	[Plasma] kwin	Reporter:	Logan Mathis <jlsuckers>
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	nate, plasma-bugs, xaver.hugl
Priority:	NOR	Keywords:	drkonqi, wayland
Version:	5.21.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	dump from coredumpctl

Description Logan Mathis 2021-09-06 19:34:33 UTC

Application: plasmashell (5.21.4)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.0-31-generic x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.4
Distribution: Ubuntu 21.04

-- Information about the crash:
- What I was doing when the application crashed:
I use my computer to to math homework, and I have an S-Pen enabled device. It seems to be connected as a mouse in the input devices, however inputs such as pressure and distance work perfectly in wayland. When I click on the draggable part of a window with my S Pen, it doesn't drag but the window goes transparent. If I move my mouse, the drag begins and the crash is avoided. If I switch windows with the window transparent, it crashes. If I use touch to move the window, the crash is avoided.
I boot in CSM mode if that has anything to do with it.
- Unusual behavior I noticed:

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007fdf21da8864 in __GI_abort () at abort.c:79
#6  0x00007fdf22219c77 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fdf20092d39 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#8  0x00007fdf200a1f9a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#9  0x00007fdf22479600 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fdf2247cbe3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fdf2247d413 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fdf2311d783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007fdf224417ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fdf2249be05 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fdf2080f8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007fdf20862d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fdf2080d023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fdf2249b204 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007fdf2244011b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fdf22448604 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x000055a862d9ae5e in ?? ()
#22 0x00007fdf21daa565 in __libc_start_main (main=0x55a862d99f10, argc=1, argv=0x7ffcd607c548, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcd607c538) at ../csu/libc-start.c:332
#23 0x000055a862d9af8e in ?? ()
[Inferior 1 (process 1022) detached]

The reporter indicates this bug may be a duplicate of or related to bug 439321, bug 438373.

Possible duplicates by query: bug 441522, bug 441421, bug 441365, bug 441234, bug 441022.

Reported using DrKonqi

Comment 1 Zamundaaa 2021-09-21 09:44:59 UTC

KWin is crashing, plasmashell just dies with it. Can you provide the backtrace of the KWin crash? You can do that by executing "coredumpctl debug kwin_wayland" and then "bt" to get the backtrace

Comment 2 Vlad Zahorodnii 2021-09-30 11:29:32 UTC

We need a backtrace of the crash to fix it? Can you please check kwin's coredumps? 

    coredumpctl list kwin_wayland

if there's one, run

    coredumpctl gdb <pid>

where <pid> is the pid from coredumpctl list output.

If you're unable to reproduce the crash, I suggest to test 5.23, which has a fix for a similar (or maybe the same?) crash.

Comment 3 Vlad Zahorodnii 2021-09-30 11:29:47 UTC

to fix it.*

Comment 4 Logan Mathis 2021-09-30 20:39:59 UTC

Created attachment 142039 [details]
dump from coredumpctl

Comment 5 Logan Mathis 2021-09-30 20:41:53 UTC

Apologies for the wait. I moved to a different desktop environment because I needed the computer working properly for school. I was able to boot off a live usb to Kubuntu, and replicate the issue. I also found out the issue is only present with Google Chrome, all other windows refuse to be dragged by the S-Pen. The dump is pretty small, so I might just have to install Kubuntu again.

Comment 6 Vlad Zahorodnii 2021-10-01 06:59:14 UTC

The backtrace is incomplete. I suggest to wait for 5.23.

Comment 7 Bug Janitor Service 2021-10-16 04:35:26 UTC

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!

Comment 8 Bug Janitor Service 2021-10-31 04:35:11 UTC

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!