Bug 477213 - Dolphin crashes on monitor turn on when DP is being used
Summary: Dolphin crashes on monitor turn on when DP is being used
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 23.08.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-11-19 00:03 UTC by mozo
Modified: 2023-12-05 12:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mozo 2023-11-19 00:03:39 UTC
Application: dolphin (23.08.3)

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.6.1-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
Dolphin crashes on monitor turn on when DP is being used. The machine is working. I just turn off my monitor, go to lunch or something, when I return and turn on the monitor, Dolphin sometimes crashes immediately. It never happens if I'm using HDMI.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#5  0x00007fd18af2757b in  () at /usr/lib/libQt5XcbQpa.so.5
#6  0x00007fd18af27b37 in  () at /usr/lib/libQt5XcbQpa.so.5
#7  0x00007fd18af2848e in  () at /usr/lib/libQt5XcbQpa.so.5
#8  0x00007fd1916ea5f7 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () at /usr/lib/libQt5Gui.so.5
#9  0x00007fd191d82a91 in  () at /usr/lib/libQt5Widgets.so.5
#10 0x00007fd191d82fe5 in  () at /usr/lib/libQt5Widgets.so.5
#11 0x00007fd191d846ed in  () at /usr/lib/libQt5Widgets.so.5
#12 0x00007fd191dd0a20 in  () at /usr/lib/libQt5Widgets.so.5
#13 0x00007fd191d788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#14 0x00007fd19109c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x564010e85f90, event=0x7ffc120d4130) at kernel/qcoreapplication.cpp:1064
#15 0x00007fd191545996 in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () at /usr/lib/libQt5Gui.so.5
#16 0x00007fd19152a6e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#17 0x00007fd18af2f5e0 in  () at /usr/lib/libQt5XcbQpa.so.5
#18 0x00007fd18f10df69 in g_main_dispatch (context=0x7fd184000ec0) at ../glib/glib/gmain.c:3476
#19 0x00007fd18f16c327 in g_main_context_dispatch_unlocked (context=0x7fd184000ec0) at ../glib/glib/gmain.c:4284
#20 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7fd184000ec0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4349
#21 0x00007fd18f10c162 in g_main_context_iteration (context=0x7fd184000ec0, may_block=1) at ../glib/glib/gmain.c:4414
#22 0x00007fd1910eaf7c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x56401075ed30, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x00007fd19109ae74 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc120d4420, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x00007fd19109c313 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x000056400ede8db8 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dolphin/dolphin-23.08.3/src/main.cpp:255
[Inferior 1 (process 3218) detached]

Reported using DrKonqi
Comment 1 mozo 2023-11-25 12:48:52 UTC
Actually this is a very old bug. I noticed it at least 2 years ago but I thought it's my old 1080Ti fault. Now I bought 4090 and the problem is still here.
Comment 2 David Edmundson 2023-12-05 11:33:58 UTC
This crash is deep in Qt. Lets take it upstream if we see issues with Qt6
Comment 3 mozo 2023-12-05 12:03:37 UTC
It's strange nobody report it for all these years. Is it only for my setup? I thought it's may be my old GTX 1080Ti but now I bought RTX 4090 and it's the same. I already tried three different DP cables. And it happens only in KDE.