Bug 491190

Summary: Dolphin crash
Product: [Applications] dolphin Reporter: Cody Johnson <codyj>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: crash CC: kfm-devel, sitter
Priority: NOR Keywords: drkonqi
Version: 22.12.3   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Cody Johnson 2024-08-02 20:13:38 UTC
Application: dolphin (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-23-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Dolphin crashing typically after desktop system goes idle and is fairly repeatable.

I tried installing packages with debug symbols via this guide https://wiki.debian.org/HowToGetABacktrace but was unsuccessful in creating a more meaningful backtrace.

I'm also running the same version of Dolphin on a laptop so I am suspecting it is possibly related to an external drive going idle.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:273
#5  0x00007f855d4f114a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x00007f855d4f1749 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x00007f855d4f2089 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x00007f8563901202 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x00007f8563f705ef in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f8563f72179 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f8563f74318 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f8563fbd421 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f8563fc11bb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f8563f62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f85632b1738 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f856373991c in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x00007f8563711cec in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f855d4fbeca in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x00007f8560fd47a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f8560fd4a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f8560fd4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f8563309876 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f85632b01bb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f85632b8316 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x0000558fa2038142 in ?? ()
#26 0x00007f8562e4624a in __libc_start_call_main (main=main@entry=0x558fa2036ed0, argc=argc@entry=1, argv=argv@entry=0x7ffedc9ac1f8) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x00007f8562e46305 in __libc_start_main_impl (main=0x558fa2036ed0, argc=1, argv=0x7ffedc9ac1f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffedc9ac1e8) at ../csu/libc-start.c:360
#28 0x0000558fa2038591 in ?? ()
[Inferior 1 (process 3623) detached]

Reported using DrKonqi
Comment 1 Harald Sitter 2024-08-02 21:34:04 UTC
Thank you for the bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), and 22.12 is no longer eligible for support or maintenance from KDE. It's possible that the issue exists only in Debian at this point.

Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.
Thanks for understanding!

Thanks again!
Comment 2 Cody Johnson 2024-08-03 19:58:26 UTC
Will do. Thank you.