Summary: | Spectacle crashes when capturing screenshot with GUI open. | ||
---|---|---|---|
Product: | [Applications] Spectacle | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
Component: | General | Assignee: | Noah Davis <noahadvs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kde |
Priority: | NOR | ||
Version: | 23.08.4 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Trace logs.
Error log. |
Description
Roke Julian Lockhart Beedell
2023-09-03 20:54:51 UTC
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. |