Bug 488670 - Freeze with black screen when trying to enter the Wayland session
Summary: Freeze with black screen when trying to enter the Wayland session
Status: RESOLVED DUPLICATE of bug 488941
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: git-stable-Plasma/6.1
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-18 15:14 UTC by soee
Modified: 2024-07-04 18:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Working config (1.38 KB, application/json)
2024-06-18 16:31 UTC, soee
Details
Failing config (1.38 KB, application/json)
2024-06-18 16:31 UTC, soee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description soee 2024-06-18 15:14:00 UTC
SUMMARY

Some scenario leads to a situation when trying to login to Wayland session the PC just freezes after SDDM with black screen and white _ in the upper left corner of the screen.

STEPS TO REPRODUCE

I am not sure how to reproduce it. I am sure it has something to do with playing with the Display Settings where we can set the refresh rate, adaptive synchronization, color profile etc.

I had this situation twice already. I was playing with the display setting to test poor performance on the Nvidia GPU.
I was changing the refresh rate, adaptive synchronization, once set build in color profile. 
There were no crashes when playing with tho settings, just PC freeze after reboot and login with SDDM.

There is one workaround/manual fix which allows me to restore my desktop and use Wayland session:
- enter recovery mode or CLI when not in any active session
- remove file: ~/.config/kwinoutputconfig.json

After that i can login just fine. I have notification that i am running in the graphics safe mode (nomodeset) but after next reboot/login its gone any my desktop works fine.

Looking at logs i'v seen such entries for example:

cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. and are incompatible
cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_wayland_drm: Checking test buffer failed!
cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_core: Applying output config failed!

OBSERVED RESULT

The PC sometimes freezes when trying to enter Wayland session.

EXPECTED RESULT

Wayland session should work fine without any PC freezes.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 6.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
GPU: Nvidia 4080
GPU Driver Version: 555.52.04

ADDITIONAL INFORMATION

I am not sure what causes this problem and i am not 100% sure if it is some bug, but i am posting it here as maybe someone can confirm it.
Comment 1 ssergio-ll 2024-06-18 15:36:20 UTC
I have also had this bug. Applying the workaround fixed it.

My system:

Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 62.7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: Micro-Star International Co., Ltd.
Product Name: GS75 Stealth 8SE
System Version: REV:1.0
Nvidia Drivers v555.52.04 open.
Comment 2 Zamundaaa 2024-06-18 16:18:20 UTC
Please attach the output config that caused the breakage, and the default that KWin generated after deleting / moving the old one. We need to know which setting causes this.

(In reply to ssergio-ll from comment #1)
> Graphics Processor: llvmpipe
Just FYI, you're getting software rendering, there's something wrong with your graphics driver setup.
Comment 3 soee 2024-06-18 16:31:09 UTC
Created attachment 170598 [details]
Working config
Comment 4 soee 2024-06-18 16:31:22 UTC
Created attachment 170599 [details]
Failing config
Comment 5 soee 2024-06-18 16:33:19 UTC
I have posted 2 configs: 1 working and 1 failing, the one working is not the default one though (i have played with settings a bit, so it probably was updated).
Comment 6 soee 2024-06-18 16:51:27 UTC
Ok i did one test:

- i have enabled HDR
- i have rebooted
- session failed to start with black screen
- i have set highDynamicRange: false
- reboot and session still failed to start
- i have set wideColorGamut: false
- reboot and session starts fine
Comment 7 Bug Janitor Service 2024-07-03 03:47:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Zamundaaa 2024-07-04 18:42:56 UTC
Ah, it's the same thing as bug 488941, where using the shadow buffer for blending somehow doesn't work

*** This bug has been marked as a duplicate of bug 488941 ***