https://bugs.kde.org/show_bug.cgi?id=517945
Bug ID: 517945
Summary: One of two screens turns black after unlocking
Classification: Plasma
Product: kwin
Version First 6.6.3
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
I have two identical screens (same model, resolution, etc). Primary screen on
the left, secondary on the right. If I lock the session and then unlock it (the
screens stay on in the meantime), Plasma is shown for maybe half a second on
the secondary (right) screen, after that it turns black. It does not switch to
standby mode, so there is still some signal, and Plasma still acts like there
are two screens. Picture is restored if I turn the affected screen off and back
on again. This is on Wayland, GPU is a Radeon 6600XT, kernel 6.19.8.
STEPS TO REPRODUCE
1. lock the session
2. unlock the session
OBSERVED RESULT
secondary screen turns black
EXPECTED RESULT
picture on secondary screen
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
ADDITIONAL INFORMATION
Possibly relevant snippent from the user log:
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:31:56 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:32:37 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
ddca_set_non_table_vcp_value -3023
Mar 21 12:32:37 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
"U28P2G6B" retrying to set DDC/CI brightness in 1000 milliseconds - attempt no.
1
Mar 21 12:32:38 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
ddca_set_non_table_vcp_value -3023
Mar 21 12:32:38 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
"U28P2G6B" retrying to set DDC/CI brightness in 2000 milliseconds - attempt no.
2
Mar 21 12:32:44 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:32:44 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:32:44 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:32:44 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
ddca_set_non_table_vcp_value -3023
Mar 21 12:32:44 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
"U28P2G6B" retrying to set DDC/CI brightness in 1000 milliseconds - attempt no.
1
Mar 21 12:32:44 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:32:44 StargateCommand kwin_wayland[1467]: atomic commit failed:
Device or resource busy
Mar 21 12:32:45 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
ddca_set_non_table_vcp_value -3023
Mar 21 12:32:45 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
"U28P2G6B" retrying to set DDC/CI brightness in 2000 milliseconds - attempt no.
2
Mar 21 12:32:47 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
ddca_set_non_table_vcp_value -3023
Mar 21 12:32:47 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
"U28P2G6B" retrying to set DDC/CI brightness in 1000 milliseconds - attempt no.
1
Mar 21 12:32:48 StargateCommand org_kde_powerdevil[1769]: [DDCutilDisplay]:
"U28P2G6B" succeeded to set DDC/CI brightness
The system log also shows this:
Mar 21 12:31:56 StargateCommand kernel: amdgpu 0000:0d:00.0: [drm] REG_WAIT
timeout 1us * 100000 tries - mpc2_assert_idle_mpcc line:481
--
You are receiving this mail because:
You are watching all bug changes.
