| Summary: | Spectacle can't screen rectangle region as normal in multimonitor setup after update to 24.08.3 | ||
|---|---|---|---|
| Product: | [Applications] Spectacle | Reporter: | Egor Kuznetsov <egor.kuznetsov.26> |
| Component: | General | Assignee: | Noah Davis <noahadvs> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | andrea.ippo, ArcangelZero7, dave, fabian, kde.usage078, kde, logan.clarke, marcela.maslanova, miguel, mtrento |
| Priority: | HI | ||
| Version First Reported In: | 24.08.3 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Example of image when press Rectangular Region | ||
After update to Frameworks 6.8.0 from 6.7.0 rectangle picker now appears as normal, but bug still alive and I see centred image as on screenshot and spectacle[5594]: qrc:/qt/qml/org/kde/spectacle/private/Gui/ImageCaptureOverlay.qml:40: ReferenceError: screenToFollow Maybe that informaton would be useful *** Bug 496139 has been marked as a duplicate of this bug. *** *** Bug 496171 has been marked as a duplicate of this bug. *** It's a regression caused by a qtdeclarative patch which fixes https://bugs.kde.org/show_bug.cgi?id=494804. Solution is to apply https://codereview.qt-project.org/c/qt/qtdeclarative/+/603331 instead of the previous https://codereview.qt-project.org/c/qt/qtdeclarative/+/601299 *** Bug 496187 has been marked as a duplicate of this bug. *** *** Bug 496183 has been marked as a duplicate of this bug. *** *** Bug 496204 has been marked as a duplicate of this bug. *** (In reply to Fabian Vogt from comment #4) > It's a regression caused by a qtdeclarative patch which fixes > https://bugs.kde.org/show_bug.cgi?id=494804. > > Solution is to apply > https://codereview.qt-project.org/c/qt/qtdeclarative/+/603331 instead of the > previous https://codereview.qt-project.org/c/qt/qtdeclarative/+/601299 Just requesting some quick clarification, as there are a lot of reports concerning this issue. Will this fix be pushed automatically in the coming days/weeks or is manual action required to resolve this for everyone affected? Thanks so much (In reply to David S from comment #8) > (In reply to Fabian Vogt from comment #4) > > It's a regression caused by a qtdeclarative patch which fixes > > https://bugs.kde.org/show_bug.cgi?id=494804. > > > > Solution is to apply > > https://codereview.qt-project.org/c/qt/qtdeclarative/+/603331 instead of the > > previous https://codereview.qt-project.org/c/qt/qtdeclarative/+/601299 > > Just requesting some quick clarification, as there are a lot of reports > concerning this issue. Will this fix be pushed automatically in the coming > days/weeks or is manual action required to resolve this for everyone > affected? Thanks so much For Tumbleweed it'll be part of the next updates. (In reply to Fabian Vogt from comment #9) > (In reply to David S from comment #8) > > (In reply to Fabian Vogt from comment #4) > > > It's a regression caused by a qtdeclarative patch which fixes > > > https://bugs.kde.org/show_bug.cgi?id=494804. > > > > > > Solution is to apply > > > https://codereview.qt-project.org/c/qt/qtdeclarative/+/603331 instead of the > > > previous https://codereview.qt-project.org/c/qt/qtdeclarative/+/601299 > > > > Just requesting some quick clarification, as there are a lot of reports > > concerning this issue. Will this fix be pushed automatically in the coming > > days/weeks or is manual action required to resolve this for everyone > > affected? Thanks so much > > For Tumbleweed it'll be part of the next updates. Hi Fabian, I'm exactly on Tumbleweed, did an update this morning to snapshot 20241113 and can no longer reproduce, which is great. I wonder however which package contained the fix - I don't seem to recall any qt updates, it was really just build numbers bumped, IIRC. Could you please point out the package(s) that included the fix? Thanks :) (In reply to Andrea Ippolito from comment #10) > (In reply to Fabian Vogt from comment #9) > > (In reply to David S from comment #8) > > > (In reply to Fabian Vogt from comment #4) > > > > It's a regression caused by a qtdeclarative patch which fixes > > > > https://bugs.kde.org/show_bug.cgi?id=494804. > > > > > > > > Solution is to apply > > > > https://codereview.qt-project.org/c/qt/qtdeclarative/+/603331 instead of the > > > > previous https://codereview.qt-project.org/c/qt/qtdeclarative/+/601299 > > > > > > Just requesting some quick clarification, as there are a lot of reports > > > concerning this issue. Will this fix be pushed automatically in the coming > > > days/weeks or is manual action required to resolve this for everyone > > > affected? Thanks so much > > > > For Tumbleweed it'll be part of the next updates. > > Hi Fabian, I'm exactly on Tumbleweed, did an update this morning to snapshot > 20241113 and can no longer reproduce, which is great. > > I wonder however which package contained the fix - I don't seem to recall > any qt updates, it was really just build numbers bumped, IIRC. > > Could you please point out the package(s) that included the fix? Thanks :) libQt6Qml* |
Created attachment 175714 [details] Example of image when press Rectangular Region SUMMARY After update Spectacle to 24.08.3 version, I can not screen rectangle region when 2 monitors pluged, cause image moved as on screenshot and rectangle picker doesen't show. STEPS TO REPRODUCE 1. Plug 2 monitors 2. Open Spectacle and select Rectangular region 3. You see a bug OBSERVED RESULT Image from 2 monitors moved to the right and duplicated and rectangle picker disappeared EXPECTED RESULT I can screen normal, image doesen't move as on screenshot and rectangle picker not disappears SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20241108 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.6-2-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: ASUS ADDITIONAL INFORMATION When I made a Screenshot, screenshot captures as normal. Bug appears only in making process. Spectacle writes spectacle[5594]: qrc:/qt/qml/org/kde/spectacle/private/Gui/ImageCaptureOverlay.qml:40: ReferenceError: screenToFollow is not defined after screenshoting