Bug 483761 - Samsung HDR unable to be turned on
Summary: Samsung HDR unable to be turned on
Status: RESOLVED DUPLICATE of bug 483697
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 6.0.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-16 13:12 UTC by kodatarule
Modified: 2024-04-02 17:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kodatarule 2024-03-16 13:12:12 UTC
SUMMARY
***
When enabling HDR to my 4K Samsung TV QLED, it just freezes and then after 30-40 seconds I am to change modes again and disable HDR to correct it
***


STEPS TO REPRODUCE
1. Enabling HDR on 4K Samsung TV


OBSERVED RESULT
just freeze without turning HDR or any indication of it working

EXPECTED RESULT
to work just as it is on my 2 DisplayPort Monitors, Tried different cable with same results

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-x64v3-xanmod1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2

ADDITIONAL INFORMATION
Additionally I also experience this on my Laptop which uses AMD+Nvidia prime, same OS, Steam Deck through Gamescope works correctly with the TV.
Comment 1 kodatarule 2024-04-02 17:06:01 UTC
I was able to track more info in regards to this, when the freeze occur in journal this message is flooding it until it reverts to regular back.

kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
kwin_wayland_drm: Checking test buffer failed!
kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Comment 2 kodatarule 2024-04-02 17:12:09 UTC

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