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

            Bug ID: 451938
           Summary: Triple Monitor via Displayport Crash on monitor Wake
           Product: plasmashell
           Version: 5.24.3
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: Multi-screen support
          Assignee: plasma-b...@kde.org
          Reporter: jason.ze...@gmail.com
                CC: aleix...@kde.org, notm...@gmail.com
  Target Milestone: 1.0

Created attachment 147747
  --> https://bugs.kde.org/attachment.cgi?id=147747&action=edit
Screen Frozen on

SUMMARY
Plasma Freezes with severe graphical distortions when waking monitors up from
sleep. 

I have an AMD Radeon RX 5700 XT with three displayport monitors hooked up to
it.  I have these monitors set to sleep after 20 minutes of no activity, the
rest of the system never sleeps/hibernates. When moving the mouse or pressing a
key the monitors will wake up and 9 times out of 10 the screen with freeze /
crash. The monitors are set up in this pattern:

Monitor 2 | Monitor 3
           Monitor 1

Monitor 1 (Main) is an Asus 34inch PG348 running at a resolution of 3440x1440
Monitors 2 and 3 are Acer 27inch XF270H with a resolution of 1920x1080

Here is a picture of what the screens do when trying to wake them up:
[img]https://i.imgur.com/nhYQ4fg.jpg[/img]

What you're seeing is the desktop of monitor 3 freaking out on monitor 1. Once
this happens the only way to bring the system back up is to press the reset
button on the front, Ctrl+Alt+f2/f3/etc do nothing.

I tend to use Monitor 3 during the week for work, I have it hooked up to my
work laptop with an hdmi cable and I just change the input to that. This past
week I have left monitor 3 connected to my laptop and not once did I experience
a system lock when waking up the screens. I suspect this has something to do
with plasma handling 2 displayport monitors fine since it doesn't see the 3rd
one that is connected to my laptop via hdmi.

Other System Info
OS: Garuda Linux x86_64 
Kernel: 5.16.16-zen1-1-zen 
Uptime: 15 mins 
Packages: 1825 (pacman) 
Shell: zsh 5.8.1 
Resolution: 3440x1440, 1920x1080, 1920x1080 
DE: Plasma 5.24.3 
WM: KWin 
Theme: Breeze Dark [Plasma], Breeze [GTK2] 
Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] 
Terminal: tilix 
CPU: AMD Ryzen 5 3600X (12) @ 3.800GHz [32.2°on] 
GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT 
Memory: 9067MiB / 64290MiB 


NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Xorg Log Errors:
cat Xorg.0.log | grep '(EE)'
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     9.247] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     9.248] (EE) Failed to load module "vesa" (module does not exist, 0)
[   247.493] (EE) event23 - Logitech MX Ergo: client bug: event processing
lagging behind by 33ms, your system is too slow
[   255.919] (EE) event23 - Logitech MX Ergo: client bug: event processing
lagging behind by 25ms, your system is too slow
[  1114.597] (EE) client bug: timer event23 debounce short: scheduled expiry is
in the past (-20ms), your system is too slow
[  1369.055] (EE) AMDGPU(0): failed to set mode: Permission denied
[  1369.055] (EE) AMDGPU(0): failed to set mode: Permission denied
[  1369.055] (EE) AMDGPU(0): failed to set mode: Permission denied


STEPS TO REPRODUCE
1. Hook three monitors up via displayport
2.  Set monitors to sleep after a few minutes
3. Wake monitors up via mouse movement or keyboard key


OBSERVED RESULT
System hard locks / freezes

EXPECTED RESULT
System doesn't freeze / wake up and can resume use

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Garuda Linux x86_64
KDE Plasma Version:  Plasma 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version:  QMake version 3.1- Using Qt version 5.15.3 in /usr/lib
Kernel Version: 5.16.16-zen1-1-zen (64-bit)
Graphics Platform: X11

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

Reply via email to