Created attachment 161384 [details] Trace logs. SUMMARY I'm unable to capture screenshots unless I use a key binding. If I use a key binding, the screenshot is captured successfully. STEPS TO REPRODUCE 1. Invoke Spectacle's GUI. 2. Use any of the capture buttons. OBSERVED RESULT Spectacle crashes. EXPECTED RESULT It obviously shouldn't. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230828 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 46.9 GiB of RAM Graphics Processor: AMD Radeon RX 5700 ADDITIONAL INFORMATION *Not git-master, 23.11.0.* From https://en.opensuse.org/SDB:KDE_repositories#Unstable_Frameworks,_Plasma_and_Applications Trying to report this causes https://discuss.kde.org/t/can-i-save-a-bug-report-from-dr-konqi-whilst-submitting-it/4698?u=rokejulianlockhart, hence the manually uploaded kcrash file.
Please modify https://bugs.kde.org/page.cgi?id=fields.html#importance to be Crash.
It turns out that invoking a key combination to capture a screenshot does cause it to crash when the GUI is visible, so the cause must be capturing a screenshot with the GUI visible, regardless of invocation method.
Created attachment 161435 [details] Error log. https://bugs.kde.org/show_bug.cgi?id=474115#c3 <blockQuote> <blockQuote> <code> PS /home/rokejulianlockhart> spectacle qrc:/src/Gui/DialogPage.qml:117:9: QML CaptureSettingsColumn (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" 23 -- exe=/usr/bin/spectacle 13 -- platform=xcb 11 -- display=:0 18 -- appname=spectacle 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=17922 20 -- appversion=23.11.70 22 -- programname=Spectacle 31 -- bugaddress=submit@bugs.kde.org KCrash: Application 'spectacle' crashing... KCrash: Attempting to start /usr/libexec/drkonqi QSocketNotifier: Invalid socket 5 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. NativeCommandExitException: Program "spectacle" ended with non-zero exit code: 139. PS /home/rokejulianlockhart> <code> </blockQuote> </blockQuote>
Do you still have this bug? I can't recall seeing something like this previously and I can't reproduce this.
(In reply to Noah Davis from comment #4) > Do you still have this bug? Not that I know of.