| Summary: | [NVIDIA] Wayland session fails to start after computer reboot | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Konrad <konrad.hossmann> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version First Reported In: | 6.0.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kwinoutputconfig.json before reboot
kwinoutputconfig.json after reboot |
||
Created attachment 168514 [details]
kwinoutputconfig.json after reboot
I add kwinoutputconfig.json which I get after reboot, when the session fails to start
I found out that if I do not change refresh rate from 60Hz to 144Hz, everything is fine and Wayland session loads properly. Only when I set my main display to 144Hz, the issue appears and Wayland session is no longer starting. |
Created attachment 168513 [details] kwinoutputconfig.json before reboot SUMMARY When I start a new session with Wayland, I change scaling of my displays to 200% each and rearrange them. After that I set middle monitor refresh rate to 144Hz from 60Hz. Everything works fine, but then after I reboot my computer, Wayland session fails to start. All three screens are blinking, can't get into another tty. I use another account to get into X11 session and delete kwinoutputconfig.json file from affected account configuration files. After reboot, new kwinoutputconfig.json is created and everything works, until I do the changes that I mentioned. STEPS TO REPRODUCE 1. Start Wayland session 2. Set display scaling to 200%, refresh rate to 144Hz 3. Reboot 4. Wayland session no longer starts OBSERVED RESULT Failure to start session EXPECTED RESULT Configurations are properly applied and session should start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.8.4-arch1-1 (64-bit) KDE Plasma Version: 6.0.3 (issue is since Beta 2) KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I have this issue since Plasma 6 Beta 2 and only on Wayland session