Bug 485959 - Spectacle doesn't open when there are two screens
Summary: Spectacle doesn't open when there are two screens
Status: RESOLVED DUPLICATE of bug 485352
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2024-04-22 13:23 UTC by Fushan Wen
Modified: 2024-04-25 20:40 UTC (History)
2 users (show)

See Also:
Latest Commit: https://invent.kde.org/plasma/kwin/-/commit/bc29e09d882d13a3a099867ba869742cd2fdb478
Version Fixed In: 6.1

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Fushan Wen 2024-04-22 13:23:47 UTC 
Two screens 4K external + 1080p internal
Spectacle master at https://invent.kde.org/graphics/spectacle/-/commit/7b75db560675715b42b27f4919ef050cbb88aa89
Qt 6.7.0
X11

Works fine on 24.02
Comment 1 Noah Davis 2024-04-22 19:49:01 UTC 
> Two screens 4K external + 1080p internal

Can you post their arrangement and scale factors?
Comment 2 Noah Davis 2024-04-22 21:19:49 UTC 
I can reproduce the issue, but I don't know what caused it.
Comment 3 Noah Davis 2024-04-22 21:21:13 UTC 
it seems like having two screens and taking a multi-screen screenshot or rectangle screenshot is enough to reproduce the issue.
Comment 4 Noah Davis 2024-04-23 20:32:42 UTC 
It seems that it's possible to take a screenshot of at least 1 screen on X11, but the request for a screenshot of the 2nd screen fails and times out after 25 seconds (the default timeout for DBus). If nobody can figure out how to fix this before May 9th, I'll have to go back to using the XCB screenshot platform plugin for X11 :/. That's a bit of a shame because it means the behavior on X11 and Wayland will no longer be consistent.
Comment 5 Christophe Marin 2024-04-25 17:19:27 UTC 
Also see https://bugs.kde.org/show_bug.cgi?id=485352
Comment 6 Noah Davis 2024-04-25 20:40:27 UTC 
Marking as a duplicate of bug 485352 since that one came first

*** This bug has been marked as a duplicate of bug 485352 ***