Bug 445771 - Resizing form crashes desktop
Summary: Resizing form crashes desktop
Status: RESOLVED LATER
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-11-19 20:15 UTC by emil.sodergren
Modified: 2022-01-07 21:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description emil.sodergren 2021-11-19 20:15:15 UTC
Application: kdeconnectd (21.08.3)

Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.13.0-21-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 21.10
DrKonqi: 5.23.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Resizing the Steam Client by alt+right click dragging from the bottom right.
This happens very frequently. I also noticed that the mouse pointer often is replaced by a pointer sized miniature of a window I have rezised before, often my konsole terminal window, right before this happens.
I am running GTX 1080 with nvidia-driver-470.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139753615846976) at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139753615846976) at pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139753615846976, signo=signo@entry=6) at pthread_kill.c:91
#7  0x00007f1af0987476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f1af096d7b7 in __GI_abort () at abort.c:79
#9  0x00007f1af0e14ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f1aef1cde45 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x00007f1aef1de06a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007f1af1074a88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f1af1077f63 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f1af1078793 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f1af1bbd6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f1af103d16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f1af1097155 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f1aef6048bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f1aef657f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f1aef602003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f1af1096548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f1af103ba9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f1af1044024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x0000562d0d6a2f9e in ?? ()
#25 0x00007f1af096efd0 in __libc_start_call_main (main=main@entry=0x562d0d6a2b70, argc=argc@entry=1, argv=argv@entry=0x7ffcbedc2588) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007f1af096f07d in __libc_start_main_impl (main=0x562d0d6a2b70, argc=1, argv=0x7ffcbedc2588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcbedc2578) at ../csu/libc-start.c:409
#27 0x0000562d0d6a3225 in _start ()
[Inferior 1 (process 1523) detached]

Reported using DrKonqi
Comment 1 Nicolas Fella 2022-01-07 21:01:45 UTC
What most likely happend is that kwin crashed, which currently takes all open programs with it. That's unfortunate and will get fixed eventually, and is not specific to KDE Connect.

What would be interesting is a crash report for kwin so we can figure out why it crashed in the first place
Comment 2 emil.sodergren 2022-01-07 21:36:18 UTC
(In reply to Nicolas Fella from comment #1)
> What most likely happend is that kwin crashed, which currently takes all
> open programs with it. That's unfortunate and will get fixed eventually, and
> is not specific to KDE Connect.
> 
> What would be interesting is a crash report for kwin so we can figure out
> why it crashed in the first place

I have not been able to reproduce this crash since I installed a debug package. However, I can make two windows "share rendering" and at the same time the mouse cursor becomes a miniature of one of the windows. When resizing Konsole with Alt+Right Mouse Drag and ending the resize ontop of a Brave browser window they both show the Konsole content. When resizing the browser both show that content. The "false" view gets weird aspect ratio but is otherwise a perfect mirror of the other window.

This behavior was immediately followed by the forementioned crash before, but now the crash does not happen any more so I do not get any logs...