Summary: | enabling HDR for projector screen results in system freeze | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | geissfl <florian.geisser.personal> |
Component: | colour-management | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | nate, xaver.hugl |
Priority: | NOR | ||
Version First Reported In: | 6.3.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
geissfl
2025-04-26 11:25:57 UTC
The framebuffer warnings are a driver issue, which becomes more visible when setting the configuration doesn't work. Please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to get a drm debug log of the issue. Hopefully it'll reveal the actual underlying problem. I started logging and enabled HDR shortly afterwards (perhaps 1-2 seconds) and stopped logging immediately once I regained control of the application. Log file is too large to upload here, let me know if this link doesn't work: https://fractalvision.spdns.org:35365/s/9ws6ErQSMnBqfCG I also added a short log file of what the log usually looks like. Not sure if it is necessary, but maybe it helps: https://fractalvision.spdns.org:35365/s/D2XTANnPs4QQ9EL Whelp, that's unfortunately entirely useless: > [drm:drm_atomic_check_only] atomic driver check for 000000000180eae3 failed: -22 That just means "the driver says no". Best I can do here is to recommend you to take this up with NVidia, at https://forums.developer.nvidia.com/c/gpu-graphics/linux if you use the proprietary driver, or at https://github.com/NVIDIA/open-gpu-kernel-modules if you use nvidia-open Aw, that's what I feared. Well, will do, thank you! |