| Summary: | Wayland session black screen no cursor, X11 black screen with cursor until reboot after plugging into external monitor | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | nathanp <nathan.w.pulver> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | duha.bugs, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
nathanp
2024-04-19 17:38:50 UTC
In the discuss thread, you mention that renaming the output config file makes it work. Does putting the old file back also break it again? For reference: The issue was resolved after deleting(renaming= ~/.config/kwinoutputconfig.json Discuss thread: https://discuss.kde.org/t/wayland-boots-to-black-screen-no-cursor-x11-boots-to-black-screen-with-cursor/14274 Broken kwinoutputconfig.json file: https://pastebin.com/gBJmH1Nm Yes I just tried this, restoring the old config json brings the issue back. I will include both the good one and the bad one here. I did change some display settings like scaling and theming once I got it working again, sorry about that hopefully it does not complicate things. The broken one: https://pastebin.com/gBJmH1Nm The working one: https://pastebin.com/Q8fMeiZx okay, I think I see what's going on. With the working config, does switching the mode to 1600x1200 trigger the issue again as well? (In reply to Zamundaaa from comment #4) > okay, I think I see what's going on. With the working config, does switching > the mode to 1600x1200 trigger the issue again as well? Yes changing the resolution to 1600x1200 from display settings while logged in causes a black screen with no cursor again. Okay, then this probably happened when you tried to mirror the laptop screen to the other screen with the same resolution. Just to confirm this is something we can prevent from happening, could you attach the output of drm_info here? (In reply to Zamundaaa from comment #6) > Okay, then this probably happened when you tried to mirror the laptop screen > to the other screen with the same resolution. > Just to confirm this is something we can prevent from happening, could you > attach the output of drm_info here? Is that the same thing as `drmdevice`? I tried installing drm_info and drminfo as well as searching for it in the arch packages repo but I cannot find anything. No. It's easy enough to compile for yourself though (https://gitlab.freedesktop.org/emersion/drm_info), but it's probably in the AUR as well (In reply to Zamundaaa from comment #8) > No. It's easy enough to compile for yourself though > (https://gitlab.freedesktop.org/emersion/drm_info), but it's probably in the > AUR as well Ok, couldn't find in AUR but yes easy enough to compile. Here is the output: https://pastebin.com/EChSCCjx Oh, the mode is advertised by the driver...
> │ │ │ ├───1600x1200@60.00 driver phsync pvsync
If you manually select that same mode on Xorg, does that have the same problem?
(In reply to Zamundaaa from comment #10) > Oh, the mode is advertised by the driver... > > │ │ │ ├───1600x1200@60.00 driver phsync pvsync > > If you manually select that same mode on Xorg, does that have the same > problem? Yep same issue in Xorg if I select 1600x1200@60 - although I am not completely sure if I set phsync or pvsy Okay, then this is on a lower level than KWin. You can create an issue at https://gitlab.freedesktop.org/drm/amd/-/issues about the broken mode. If you want, you can also follow bug 481222; when that's fixed, mirroring won't change modes anymore and would work around this issue (In reply to Zamundaaa from comment #12) > Okay, then this is on a lower level than KWin. You can create an issue at > https://gitlab.freedesktop.org/drm/amd/-/issues about the broken mode. > If you want, you can also follow bug 481222; when that's fixed, mirroring > won't change modes anymore and would work around this issue I will do this this weekend, just got a bit busier during the week. Thank you for all the help. |