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

            Bug ID: 495345
           Summary: Display monitor errors/issues after wake from sleep
    Classification: Plasma
           Product: plasma-wayland-protocols
           Version: unspecified
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

Created attachment 175229
  --> https://bugs.kde.org/attachment.cgi?id=175229&action=edit
Screen error when window move to right side of screen

SUMMARY

When waking the pc from sleep, the following occurs:
1. The default lock screen wallpaper differs from what it was on the last
successful reboot (not really a functional issue)
2. On logging in, the screen resolution changes from 5120x1440 to 3840x1440
3. On changing back to 5120, the 240hz option is not available anymore. It is
available for all resolutions below 5120
4. The right 1/5th (ish) of the screen seems to become corrupted static when a
window is place in that region. This region also seems to be variable, as in it
follows specific elements of the window when moving it around.


STEPS TO REPRODUCE
1. Reboot PC and login, no screen issue present, no display setting issues
present
2. Send PC to sleep
3. Wake PC and login, above issues occur

OBSERVED RESULT

Display setting issues and visual screen region issues occur after wake from
sleep.

EXPECTED RESULT

No issues occur, all settings remain as they were before sleep. All screen
regions remain usable and free from visual error.

SOFTWARE/OS VERSIONS
Arch Linux 6.11.5-arch1-1
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION

The resolution change and screen region errors only started occurring after my
last system update within the last week or so. These issues were not occurring
before then. It is possible this is an nvidia driver update issue, but I'm not
totally sure.

These issues do not appear after rebooting.

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

Reply via email to