https://bugs.kde.org/show_bug.cgi?id=442091

            Bug ID: 442091
           Summary: (Wayland) Plasma crashes when trying to move window
                    with S Pen (Samsung Notebook 9 Pro)
           Product: plasmashell
           Version: 5.21.4
          Platform: Ubuntu Packages
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: k...@davidedmundson.co.uk
          Reporter: jlsuck...@gmail.com
                CC: plasma-b...@kde.org
  Target Milestone: 1.0

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

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to