Screens won't turn on after manually suspending

Bug #2020709 reported by anarcochip
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kwin (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

SUMMARY
When returning from "suspend" (sleep mode), the monitors do not turn on, or rarely return with low resolution (640x480). Wayland does not allow resolution change (attachment).
I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI).

STEPS TO REPRODUCE
1. Manually suspend the computer.
2. Wait for the suspend process to finish (front panel LED flashes).
3. Press any key to wake up the computer.

OBSERVED RESULT
A1 - The screens do not turn on (monitor LED is blinking) after manual suspension.
A2 - Sometimes the screens turn on, but with low resolution (640x480).
A3 - Sometimes one of the screens returns with a resolution of 640x480 after returning from automatic suspension (when the automatic shutdown of the splint is not active).
A4 - If the screen turns off automatically (before the automatic suspension) the monitor video returns with adequate resolution (1600x900)

EXPECTED OUTCOME
The screens turn on after the computer wakes up from sleep mode.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
      OS: Kubuntu 22.04.2 LTS x86_64
      Kernel: 5.19.0-42-generic
KDE Plasma Version: 5.24.7
KDE Framework Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
To view any content, you must force restart with the power button or remove and reinsert the display cable.
I installed the amd package for the gpu but the problem remained.
https://www.amd.com/en/support/graphics/amd-radeon-6000-series/amd-radeon-6600-series/amd-radeon-rx-6600

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed May 24 17:12:50 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Navi 23 [Radeon RX 6600/6600 XT/6600M] [148c:2413]
InstallationDate: Installed on 2023-05-20 (3 days ago)
InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
MachineType: To Be Filled By O.E.M. B550M-ITX/ac
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-42-generic root=UUID=14e3583d-5b94-40f1-b1ff-0d1d175e7bc8 ro rootflags=subvol=@ quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display

anarcochip (anarochip)
description: updated
affects: xorg (Ubuntu) → kwin (Ubuntu)
anarcochip (anarochip)
description: updated
Changed in kwin (Ubuntu):
status: New → Incomplete
Revision history for this message
Scarlett Gately Moore (scarlettmoore) wrote :

I cannot find any bugs upstream for this, the closest being https://bugs.kde.org/show_bug.cgi?id=427861
I am not convinced it is kwin. I need logs of when it happens please.

sudo dmesg > dmesg.txt

journalctl -b-1 > prevboot.txt

Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.