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

            Bug ID: 516682
           Summary: OSD (volume popup) appears on wrong screen after
                    physical monitor power cycle on Wayland (Plasma 6.6.0)
    Classification: Plasma
           Product: plasmashell
      Version First 6.6.0
       Reported In:
          Platform: CachyOS
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Display Configuration widget and OSD
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 1.0

SUMMARY
OSD (volume popup) appears on wrong screen after physical monitor power cycle
on Wayland (Plasma 6.6.0)

STEPS TO REPRODUCE
1. Boot into a Plasma Wayland session.
2. Physically turn off both monitors using their power buttons.
3. Wait a few seconds, then turn the monitors back on.
4. Trigger the volume OSD (e.g., using the keyboard volume keys).

OBSERVED RESULT
The volume OSD appears in the lower-left corner of the global compositor space
(on the non-primary monitor) instead of on the primary monitor, even though the
monitor geometry is correct.

Restarting plasmashell fixes the placement.

EXPECTED RESULT
The volume OSD should appear on the primary monitor (DP-2 in my setup) after
waking the monitors.

SOFTWARE/OS VERSIONS
- Linux/KDE Plasma: CachyOS (Arch-based)
- KDE Plasma Version: 6.6.0-1.1
- KDE Frameworks Version: 6.6.0 (default from CachyOS)
- Qt Version: 6.7.3 (default from CachyOS)
- GPU / Driver: AMD Radeon RX 9070 XT, amdgpu

ADDITIONAL INFORMATION
- Two monitors connected via DisplayPort:
    - DP-1: 2560x1440 @ 60 Hz (left)
    - DP-2: 2560x1440 @ 179.85 Hz (right, primary)
- Mixed refresh rates appear to trigger the bug.
- kscreen-doctor -o confirms the output geometry is correct after monitor
reconnection:
    - DP-1: 0,0 2560x1440
    - DP-2: 2560,0 2560x1440 (primary)
- Issue affects OSD only; tray icons, notifications, and other UI elements
appear correctly.
- Does not crash the session or produce errors in logs.
- This issue began after upgrading to Plasma 6.6.0; did not occur in 6.5.x.

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

Reply via email to