Bug 458445

Summary:	KRDC crashes when clicking on "Full screen"
Product:	[Applications] krdc	Reporter:	me
Component:	general	Assignee:	Urs Wolfer <uwolfer>
Status:	RESOLVED FIXED
Severity:	crash	CC:	aacid
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	22.08.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	KRDC backtrace from GDB KRDC backtrace from GDB (2)

Description me 2022-08-28 22:53:05 UTC

Application: krdc (22.08.0)

Qt Version: 5.15.5
Frameworks Version: 5.97.0
Operating System: Linux 5.19.4-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
When I'm connected to a remote desktop and I click on the "Full screen" button, KRDC just crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KRDC (krdc), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fbe2a563154 in QScreen::geometry() const () from /usr/lib/libQt5Gui.so.5
#5  0x000055a63582c182 in ?? ()
#6  0x00007fbe2a0be280 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x00007fbe2ad6bec7 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5
#8  0x00007fbe2ad718e7 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5
#9  0x00007fbe2ae6025e in ?? () from /usr/lib/libQt5Widgets.so.5
#10 0x00007fbe2ae60460 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5
#11 0x00007fbe2af5316f in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5
#12 0x00007fbe2adaf707 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007fbe2ad78b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#14 0x00007fbe2ad7e359 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#15 0x00007fbe2a08d978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#16 0x00007fbe2ad7c357 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /usr/lib/libQt5Widgets.so.5
#17 0x00007fbe2adcd3d5 in ?? () from /usr/lib/libQt5Widgets.so.5
#18 0x00007fbe2adcf17e in ?? () from /usr/lib/libQt5Widgets.so.5
#19 0x00007fbe2ad78b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#20 0x00007fbe2a08d978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#21 0x00007fbe2a53f08c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5
#22 0x00007fbe2a528965 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#23 0x00007fbe24731af0 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#24 0x00007fbe28118c6b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007fbe2816f001 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007fbe28116392 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007fbe2a0d825c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#28 0x00007fbe2a08611c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#29 0x00007fbe2a090c49 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#30 0x000055a63581c29c in ?? ()
#31 0x00007fbe2983c2d0 in ?? () from /usr/lib/libc.so.6
#32 0x00007fbe2983c38a in __libc_start_main () from /usr/lib/libc.so.6
#33 0x000055a63581cd65 in ?? ()
[Inferior 1 (process 176516) detached]

Reported using DrKonqi

Comment 1 Albert Astals Cid 2022-08-29 22:03:00 UTC

Could you give us a backtrace with debug information? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Arch_Linux

Comment 2 me 2022-08-30 09:52:05 UTC

(In reply to Albert Astals Cid from comment #1)
> Could you give us a backtrace with debug information?
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Arch_Linux

https://0x0.st/opag.txt

Comment 3 Albert Astals Cid 2022-08-30 22:15:43 UTC

(In reply to 1sk8pp6j from comment #2)
> (In reply to Albert Astals Cid from comment #1)
> > Could you give us a backtrace with debug information?
> > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> > How_to_create_useful_crash_reports#Arch_Linux
> 
> https://0x0.st/opag.txt

That doesn't have debug information, please follow the instructions in that link, i.e. install or enable debuginfod

Not sure if that works with coredumpctl, but assuming you can reproduce the crash

gdb krdc
y
run
... make it crash ...
bt
... attach the backrace here...

Comment 4 me 2022-08-30 22:35:43 UTC

Created attachment 151714 [details]
KRDC backtrace from GDB

Comment 5 Albert Astals Cid 2022-08-30 22:40:41 UTC

You still haven't installed debuginfod so the backtrace is as bad as every time you post it.

Comment 6 me 2022-08-30 22:48:14 UTC

(In reply to Albert Astals Cid from comment #5)
> You still haven't installed debuginfod so the backtrace is as bad as every
> time you post it.

But I did install it. The instructions aren't clear.

Comment 7 me 2022-08-30 22:51:34 UTC

(In reply to 1sk8pp6j from comment #6)
> (In reply to Albert Astals Cid from comment #5)
> > You still haven't installed debuginfod so the backtrace is as bad as every
> > time you post it.
> 
> But I did install it. The instructions aren't clear.

OK so apparently I had to logout after installing debuginfod or just give gdb an environment variable, I'll update the attachment in a few moments.

Comment 8 me 2022-08-30 22:57:06 UTC

Created attachment 151715 [details]
KRDC backtrace from GDB (2)

Comment 9 Albert Astals Cid 2022-08-30 23:08:39 UTC

Do you have multiple screens? Or anything in your screen situation that you think it's "unusual?

Comment 10 me 2022-08-31 07:58:19 UTC

(In reply to Albert Astals Cid from comment #9)
> Do you have multiple screens? Or anything in your screen situation that you
> think it's "unusual?

Yes, I have a 1920x1080 HDMI monitor and two identical 1680x1050 (16:10) DVI monitors, one of which is connected with an adapter to DP because I don't have another DVI port on my graphics card.

Comment 11 Albert Astals Cid 2022-08-31 15:14:03 UTC

ok, should hopefully be fixed with https://invent.kde.org/network/krdc/commit/fdec6d33003230bfca0c08e148f7253709f246cf

If you update to 22.08.1 and still have this crash please reopen this issue