SUMMARY Gwenview crashes every time when trying to crop the attached file. STEPS TO REPRODUCE 1. Open attached file in Gwenview 2. Crop file to spine 3. Hit OK OBSERVED RESULT Gwenview crashes EXPECTED RESULT Gwenview doesn't crash, and lets me crop the file. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.2 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.8.0-52-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION This file can be successfully cropped in other programs- qimgv allowed me to crop this file successfully. The scan was produced by Skanlite 24.12.1
Created attachment 177940 [details] The backtrace for the crash The most recent crash for this- re-produced as I was gathering data for this report.
Created attachment 177941 [details] The cropped file I was trying to generate This is the file produced by qimgv after I cropped it.
Created attachment 178445 [details] The file that crashes Gwenview upon cropping Here's the file I was trying to crop, and how to reproduce this. I was trying to crop to just the CD spine- as soon as you release the mouse button to set the crop, Gwenview crashes. I've attached a half size version of the file that I confirmed still crashes on my KDE Neon system as of today. I've also tested this on a fresh install (unpatched) of Fedora KDE 41 using Gwenview 24.08.2, and it does not crash.
Thank you for the report. May we ask you to upload the backtrace to see the call stack? This bug might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=481140.
(In reply to Pedro from comment #4) > Thank you for the report. May we ask you to upload the backtrace to see the > call stack? This bug might be a duplicate of > https://bugs.kde.org/show_bug.cgi?id=481140. The original backtrace was an attachment to this bug: https://bugs.kde.org/attachment.cgi?id=177940 I just re-tested, and the crash still happens, exactly the same way. It was automatically reported, and I'm attaching the backtrace as an attachment as well.
Created attachment 179769 [details] Backtrace from re-testing tonight.
Thank you. Unfortunately, it seems it doesn't contain the required information. May we request the following: - When the application crashes, could you please click on `Report Bug` on the notification that appears on the desktop panel - then in the Crash Handler window, click on `See Developer Information` - please make sure that the checkbox `Automatically download debug symbols to enhance crash reports` is selected - wait for symbols to be downloaded and the backtrace to appear (there are 3 stars near the top right corner and a red X icon to their left. When the information is ready the X icon will disappear) - Then click on the `Save` button near the window's top right corner - Paste the content in Bugzilla as a comment or upload the document as an attachment The backtrace should have a structure like this: Application: Gwenview (gwenview), signal: Aborted Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>} [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x000071a6ea84527e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x000071a6ea8288ff in __GI_abort () at ./stdlib/abort.c:79 #9 0x000071a6eb50c1ac in qAbort () at /usr/src/qt6-base-6.8.2-0zneon+24.04+noble+release+build42/src/corelib/global/qassert.cpp:49 #10 qt_message_fatal<QString&> (message=..., context=<optimized out>) at /usr/src/qt6-base-6.8.2-0zneon+24.04+noble+release+build42/src/corelib/global/qlogging.cpp:2130 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x71a6eb242b68 "ASSERT: \"%s\" in file %s, line %d", ap=ap@entry=0x7ffe691a30a8) at /usr/src/qt6-base-6.8.2-0zneon+24.04+noble+release+build42/src/corelib/global/qlogging.cpp:382 #12 0x000071a6eb50d089 in QMessageLogger::fatal (this=this@entry=0x7ffe691a32e8, msg=msg@entry=0x71a6eb242b68 "ASSERT: \"%s\" in file %s, line %d") at /usr/src/qt6-base-6.8.2-0zneon+24.04+noble+release+build42/src/corelib/global/qlogging.cpp:884 #13 0x000071a6eb50d100 in qt_assert (assertion=assertion@entry=0x71a6ed991d1b "!(max < min)", file=file@entry=0x71a6ed98e2e8 "/usr/include/x86_64-linux-gnu/qt6/QtCore/qminmax.h", line=line@entry=25) at /usr/src/qt6-base-6.8.2-0zneon+24.04+noble+release+build42/src/corelib/global/qassert.cpp:105 #14 0x000071a6ed899741 in qBound<int>(int const&, int const&, int const&) [clone .part.0] [clone .lto_priv.0] (max=<optimized out>, val=<optimized out>, min=<optimized out>) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qminmax.h:25 #15 0x000071a6ed89a6d5 in qBound<int> (max=<optimized out>, val=<optimized out>, min=<optimized out>) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qarraydataops.h:98 ...
Created attachment 179829 [details] Crash with full backtrace After following the instructions provided, this should be the right backtrace- I saw 3 stars, and the X disappeared.
Thank you for taking the time to provide the backtrace. After reviewing it, this looks like it's caused by the same reason as https://bugs.kde.org/show_bug.cgi?id=481140. This issue is currently being addressed. Please follow that report for updates. Thanks! I'm marking it as a duplicate. *** This bug has been marked as a duplicate of bug 481140 ***