502087 – Turning on HDR on 165hz 2k Odyssey G5 monitor makes system unresponsive and lower makes the monitor unresponsive

Bug 502087 - Turning on HDR on 165hz 2k Odyssey G5 monitor makes system unresponsive and lower makes the monitor unresponsive

Summary: Turning on HDR on 165hz 2k Odyssey G5 monitor makes system unresponsive and ...

Status:	NEEDSINFO WAITINGFORINFO

Alias:	None

Product:	kwin
Classification:	Plasma
Component:	colour-management (show other bugs)
Version:	6.3.3
Platform:	Arch Linux Linux

Importance:	NOR crash
Target Milestone:	---
Assignee:	KWin default assignee

URL:
Keywords:

Depends on:
Blocks:

Reported:	2025-03-27 19:20 UTC by thankarezos
Modified:	2025-04-04 15:28 UTC (History)
CC List:	2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description thankarezos 2025-03-27 19:20:45 UTC

SUMMARY

When I try to enable HDR on odyssey g5 32 inch 2k monitor connected by display port if the refresh rate is set to 165hz, the desktop freezes fully and there is no way to recover other than turn it off forcefully. When I log in again every screen is black, and I need to forcefully shut down again go to the tty and delete the .config/kwinoutputconfig.json only then I can log in again without everything freezing, or I need to unplug the monitor but if I plug it again and the HDR was on it will freeze again. I use a lot of monitors, but it still happens with the two monitors. If I reduce the refresh rate to 144hz or lower I still can't enable HDR but the pc doesn't freeze but the HDR monitor stays black (other monitors work in this case and I don't need to forcefully shut down and remove the file to remove HDR). HDR works fine on Windows on same machine on same refresh rate. I am using a 5070 with 570.133.07 open drivers.

STEPS TO REPRODUCE
1. Set refresh rate to 165hz (or lower for similar problem)
2. enable HDR

OBSERVED RESULT
Everything freezes (all the monitors) or the HDR enabled monitor is not working

EXPECTED RESULT
Not freeze or the HDR monitor to turn on

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.12.20-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 12 × 11th Gen Intel® Core™ i5-11400F @ 2.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 5070

Comment 1 Nate Graham 2025-03-28 20:32:57 UTC

We've seen other problems with this exact monitor too; see Bug 494522.

Comment 2 Zamundaaa 2025-04-01 17:13:46 UTC

Please trigger the hang, and then attach the output of
> journalctl --user-unit plasma-kwin_wayland --boot 0
and
> journalctl -k --boot 0
here (--boot -1 if you need to shut down in between)

Comment 3 thankarezos 2025-04-04 15:27:27 UTC

(In reply to Zamundaaa from comment #2)
> Please trigger the hang, and then attach the output of
> > journalctl --user-unit plasma-kwin_wayland --boot 0
> and
> > journalctl -k --boot 0
> here (--boot -1 if you need to shut down in between)

should I do this before or after deleting the .config/kwinoutputconfig.json because if I don't delete that it stays frozen, so I can't  get the output of it, here the output anyway but maybe i need to do someething else to make it usefull

```Apr 04 18:22:11 EOS systemd[2016]: Starting KDE Window Manager...
Apr 04 18:22:11 EOS systemd[2016]: Started KDE Window Manager.
Apr 04 18:22:11 EOS kwin_wayland[3283]: No backend specified, automatically choosing drm
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3391]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3391]: > Warning:          Could not resolve keysym XF86RefreshRateTogg>
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3391]: > Warning:          Could not resolve keysym XF86Accessibility
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3391]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3391]: Errors from xkbcomp are not fatal to the X server
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: > Warning:          Unsupported maximum keycode 708, clipping.
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: >                   X11 cannot support keycodes above 255.
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: > Warning:          Could not resolve keysym XF86RefreshRateTogg>
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: > Warning:          Could not resolve keysym XF86Accessibility
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Apr 04 18:22:13 EOS kwin_wayland_wrapper[3398]: Errors from xkbcomp are not fatal to the X server
Apr 04 18:22:13 EOS kcminit[3400]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 04 18:22:13 EOS kcminit[3400]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_style.so"
Apr 04 18:22:14 EOS kwin_wayland[3283]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used >
Apr 04 18:22:14 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7dc60)
Apr 04 18:22:14 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7dc60)
Apr 04 18:22:14 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7dc60)
Apr 04 18:22:15 EOS kwin_wayland[3283]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used >
Apr 04 18:22:15 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7d8f0)
Apr 04 18:22:15 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7d8f0)
Apr 04 18:22:15 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54ff6b690)
Apr 04 18:22:16 EOS kwin_wayland[3283]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used >
Apr 04 18:22:16 EOS kwin_wayland[3283]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used >
Apr 04 18:22:19 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7d8f0)
Apr 04 18:22:19 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da54fe7d8f0)
Apr 04 18:22:26 EOS kwin_wayland[3283]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5da5502f6c20)```

Apr 04 21:21:11 EOS kernel: Linux version 6.12.21-1-lts (linux-lts@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld>
Apr 04 21:21:11 EOS kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=0cc99b00-1e58-4b01-bac6-1>
Apr 04 21:21:11 EOS kernel: BIOS-provided physical RAM map:
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000087eb0fff] usable
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000087eb1000-0x0000000087eb1fff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000087eb2000-0x0000000088f2cfff] usable
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000088f2d000-0x0000000088f2dfff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000088f2e000-0x0000000096a2ffff] usable
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000096a30000-0x0000000098f2ffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000098f30000-0x00000000991affff] ACPI data
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000991b0000-0x0000000099647fff] ACPI NVS
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000099648000-0x0000000099ffefff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000099fff000-0x0000000099ffffff] usable
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x000000009a000000-0x000000009dffffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x000000009ee00000-0x000000009fffffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Apr 04 21:21:11 EOS kernel: BIOS-e820: [mem 0x0000000100000000-0x000000085fffffff] usable
Apr 04 21:21:11 EOS kernel: The simpledrm driver will not be probed
Apr 04 21:21:11 EOS kernel: NX (Execute Disable) protection: active
Apr 04 21:21:11 EOS kernel: APIC: Static calls initialized

Comment 4 thankarezos 2025-04-04 15:28:25 UTC

(In reply to Nate Graham from comment #1)
> We've seen other problems with this exact monitor too; see Bug 494522.

disabling ddcutil helped with powercycles problems or taking a lot to wake up but not with HDR problem