https://bugs.kde.org/show_bug.cgi?id=502473

            Bug ID: 502473
           Summary: Spectacle Incorrectly Maps Capture Starting Position
                    on Primary Screen After Display Reconnection (Wayland)
    Classification: Applications
           Product: Spectacle
           Version: 6.3.3
          Platform: NixOS
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: General
          Assignee: noaha...@gmail.com
          Reporter: gjz010...@gmail.com
                CC: k...@david-redondo.de
  Target Milestone: ---

Created attachment 180042
  --> https://bugs.kde.org/attachment.cgi?id=180042&action=edit
Note that the mouse selects on Monitor 1, but the rect appears on Monitor 2.
Menu bar is cropped intentionally.

SUMMARY
Spectacle misplaces region selection starting point on primary display after
monitor reconnection sequence

STEPS TO REPRODUCE
1. Configure two displays: Display 1 (primary), Display 2 (secondary)
2. Power off both displays
3. Power on Display 1 first, followed by Display 2
4. Launch Spectacle (via "rectangular region screenshot" keyboard shortcut)
5. Observe normal behavior on both displays
6. Power cycle Display 1 (turn off then on again)
7. Attempt region selection:
   - Start selection on Display 1
   - Start selection on Display 2

OBSERVED RESULT
After Display 1 power cycle (Step 6):
- Region selection starting point on Display 1 appears offset to corresponding
position on Display 2
- Selection starting point on Display 2 remains normal

EXPECTED RESULT
Region selection starting point should always:
- Begin on the physically selected display (Display 1)
- Maintain correct spatial positioning relative to actual monitor layout

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS 25.05, 6.13.7 (64-bit)
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Graphics Platform: Wayland

ADDITIONAL INFORMATION
- Only tested on Wayland (no X11 verification)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to