https://bugs.kde.org/show_bug.cgi?id=445470
Philipp <p...@hb9etc.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |---
Status|RESOLVED |REOPENED
CC| |p...@hb9etc.ch
Ever confirmed|0 |1
--- Comment #8 from Philipp <p...@hb9etc.ch> ---
I have exactly the same problem, also with this ThinkVision M14t USB-C
touchscreen as only monitor on a machine with newly installed Kubuntu 24.04.
Packages are up-to-date.
The touchscreen is not usable at all. Whenever it is touched, the focused
application simply crashes. If no application window is open, it is plasmashell
that crashes. I wasn't able to get the the crash handler (drkonqi) to accept
the backtrace of the application (even when setting DEBUGINFOD_URLS), but here
we go, for example with Konsole:
```
Application: Konsole (konsole), signal: Segmentation fault
[KCrash Handler]
#4 0x000074e6373084a9 in QXcbConnection::xi2ProcessTouch(void*, QXcbWindow*)
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#5 0x000074e6372d31e5 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6 0x000074e6372d479f in
QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7 0x000074e6372fccff in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8 0x000074e63bb145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x000074e63bb73717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x000074e63bb13a53 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x000074e63db35279 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x000074e63dad6a7b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x000074e63dadf3e8 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x000063766ec679d4 in ?? ()
#15 0x000074e63d02a1ca in __libc_start_call_main
(main=main@entry=0x63766ec65d00, argc=argc@entry=3,
argv=argv@entry=0x7ffd5577b238) at ../sysdeps/nptl/libc_start_call_main.h:58
#16 0x000074e63d02a28b in __libc_start_main_impl (main=0x63766ec65d00, argc=3,
argv=0x7ffd5577b238, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffd5577b228) at ../csu/libc-start.c:360
#17 0x000063766ec682b5 in ?? ()
[Inferior 1 (process 3610) detached]
```
Or with the system monitor:
```
Application: Konsole (konsole), signal: Segmentation fault
[KCrash Handler]
#4 0x000074e6373084a9 in QXcbConnection::xi2ProcessTouch(void*, QXcbWindow*)
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#5 0x000074e6372d31e5 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6 0x000074e6372d479f in
QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7 0x000074e6372fccff in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8 0x000074e63bb145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x000074e63bb73717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x000074e63bb13a53 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x000074e63db35279 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x000074e63dad6a7b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x000074e63dadf3e8 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x000063766ec679d4 in ?? ()
#15 0x000074e63d02a1ca in __libc_start_call_main
(main=main@entry=0x63766ec65d00, argc=argc@entry=3,
argv=argv@entry=0x7ffd5577b238) at ../sysdeps/nptl/libc_start_call_main.h:58
#16 0x000074e63d02a28b in __libc_start_main_impl (main=0x63766ec65d00, argc=3,
argv=0x7ffd5577b238, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffd5577b228) at ../csu/libc-start.c:360
#17 0x000063766ec682b5 in ?? ()
[Inferior 1 (process 3610) detached]
```
Or drkonqi-coredump-gui:
```
Application: DrKonqi Intensive Care (drkonqi-coredump-gui), signal:
Segmentation fault
[KCrash Handler]
#4 0x00007ba15d3084a9 in QXcbConnection::xi2ProcessTouch(void*, QXcbWindow*)
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#5 0x00007ba15d2d31e5 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6 0x00007ba15d2d479f in
QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7 0x00007ba15d2fccff in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8 0x00007ba15ff145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007ba15ff73717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ba15ff13a53 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ba161735279 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ba1616d6a7b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ba1616df3e8 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x0000636c646ac256 in ?? ()
#15 0x00007ba160c2a1ca in __libc_start_call_main
(main=main@entry=0x636c646ab050, argc=argc@entry=1,
argv=argv@entry=0x7ffe3709df38) at ../sysdeps/nptl/libc_start_call_main.h:58
#16 0x00007ba160c2a28b in __libc_start_main_impl (main=0x636c646ab050, argc=1,
argv=0x7ffe3709df38, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffe3709df28) at ../csu/libc-start.c:360
#17 0x0000636c646acd05 in ?? ()
[Inferior 1 (process 4803) detached]
```
Unfortunately, I can't convince drkonqi to show me the backtrace of the
`plasmashell` crash again, I probably dismissed it too often. The same issue
does **not** happen in Firefox and probably also not in other non-Qt
applications.
The issue does **not** appear when using a Wayland session
(plasma-workspace-wayland package), but then the physical keyboard is not
working anymore after touching the screen for the first time; I also observe
this behavior on the login screen (SDDM) and therefore can't login after
touching the screen once.
This is the lsusb output of the screen:
```
Bus 003 Device 007: ID 2d1f:524c Wacom Taiwan Information Co. Ltd. Pen and
multitouch sensor
```
System/version information:
```
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-38-generic (64-bit)
Graphics Platform: X11
Processors: 18 × Intel® Core? Ultra 5 125H
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
```
--
You are receiving this mail because:
You are watching all bug changes.
