Bug 492276 - Spectacle can't access both screens in dual display setup
Summary: Spectacle can't access both screens in dual display setup
Status: REPORTED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 24.08.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-27 16:00 UTC by pumaelbusta
Modified: 2024-08-28 07:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pumaelbusta 2024-08-27 16:00:04 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1.  start spectacle

OBSERVED RESULT
error displayed, being active only on one of the displays

EXPECTED RESULT
spectacle to start normally, allowing taking screenshots of any/both screens

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.5.0-35-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520


ADDITIONAL INFORMATION
I have a 2 display setup, DP-2-1 and DP-2-2 are connected. Recently I noticed that spectacle throws and error on start ( see below) and thus it's active only on one of the dislpays (in Rectangular region mode if I move the cursor to the other display, Spectacle elements are disappearing, when I move the cursod back, they're shown again).
I see only the same message in syslog:

An error occurred while taking a screenshot.
KWin screenshot request failed:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Potentially relevant information:
- Method: CaptureScreen
- Method specific arguments: "DP-2-2"
Comment 1 pumaelbusta 2024-08-28 07:48:09 UTC
Update: This behaviour is gone after reboot - not sure what changed. Perhaps this can be closed.