Bug 507024

Summary:	Gwenview segfaults while pressing esc and getting back in (once or repeatedly)
Product:	[Applications] gwenview	Reporter:	Ángel Navarro <jesusnavarrojr188>
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	idontfeelcomfygivingyoumyemail
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	25.07.80
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:	https://crash-reports.kde.org/organizations/kde/issues/216446/events/c5620ae4876942cfa54068fc8e3dfd44/
Attachments:	New crash information added by DrKonqi

Description Ángel Navarro 2025-07-14 12:22:06 UTC

Application: gwenview (25.07.80)
 (Compiled from sources)
ApplicationNotResponding [ANR]: false
Qt Version: 6.10.0
Frameworks Version: 6.17.0
Operating System: Linux 6.15.6-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.4.2 [CoredumpBackend]

-- Information about the crash:
I exited the image to the browser by pressing "ESC" and tried to go back in, and Gwenview crashed. I could sometimes reproduce this issue by repeatedly exiting, moving the cursor around and getting back into an image.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#4  std::__atomic_base<QMutexPrivate*>::load (this=0x859, __m=std::memory_order_relaxed) at /usr/include/c++/15.1.1/bits/atomic_base.h:828
#5  std::atomic<QMutexPrivate*>::load (this=0x859, __m=std::memory_order_relaxed) at /usr/include/c++/15.1.1/atomic:587
#6  QAtomicOps<QMutexPrivate*>::loadRelaxed<QMutexPrivate*> (_q_value=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qatomic_cxx11.h:202
#7  QBasicAtomicPointer<QMutexPrivate>::loadRelaxed (this=0x859) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qbasicatomic.h:170
#8  QBasicMutex::fastTryLock (this=0x859) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qmutex.h:87
#9  QBasicMutex::lock (this=0x859) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qmutex.h:43
#10 std::unique_lock<QMutex>::lock (this=<synthetic pointer>) at /usr/include/c++/15.1.1/bits/unique_lock.h:144
#11 std::unique_lock<QMutex>::unique_lock (this=<synthetic pointer>, __m=...) at /usr/include/c++/15.1.1/bits/unique_lock.h:75
#12 (anonymous namespace)::qt_unique_lock<QMutex> (mutex=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qlocking_p.h:66
#13 QCoreApplicationPrivate::lockThreadPostEventList (object=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1589
#14 0x00007f1e8e9c4ac1 in QObject::deleteLater (this=0x56199c3b8c30) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:2441
#15 0x00007f1e8f62f87e in QBasicDrag::eventFilter (this=0x56199b68d0c0, o=0x56199c252c20, e=0x7fff463ec980) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qsimpledrag.cpp:109
#16 0x00007f1e8d911e23 in QtWaylandClient::QWaylandDrag::finishDrag (this=this@entry=0x56199b68d0c0) at /usr/src/debug/qt6-base/qtbase/src/plugins/platforms/wayland/qwaylanddnd.cpp:101
#17 0x00007f1e8d912195 in QtWaylandClient::QWaylandDataDevice::data_device_drop (this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/plugins/platforms/wayland/qwaylanddatadevice.cpp:205
#18 0x00007f1e8c8a6ac6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#19 0x00007f1e8c8a376b in ffi_call_int (cif=cif@entry=0x7fff463ecc10, fn=fn@entry=0x7f1e8d8f69d0 <QtWayland::wl_data_device::handle_drop(void*, wl_data_device*)>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7fff463ecce0, closure=closure@entry=0x0) at ../src/x86/ffi64.c:676


Reported using DrKonqi

Comment 1 Ángel Navarro 2025-07-14 12:22:08 UTC

Created attachment 183223 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 A Linux User 2025-08-18 11:48:40 UTC

Cannot reproduce. Can you make a screenrecording of the bug?

Comment 3 Bug Janitor Service 2025-09-02 03:47:24 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2025-09-17 03:48:32 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.