HDR calibration tool causes system-wide freeze

After plasma 6.7 upgrade, clicking the HDR Calibration tool causes a system wide freeze. Ctrl+Alt+F1 to F7 does nothing. Magic SysRq key is disabled so I am forced to use the power button to restart.
HDR calibration is attempted for a monitor over HDMI, which connects to Nvidia dGPU. Didn’t see any errors related to ‘nvidia’ in KSystemLog (journalctl).
System Info:

Operating System: Aurora 44
KDE Plasma Version: 6.7.0
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.9-205.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 16 GiB of RAM (14.8 GiB usable)
Graphics Processor 1: AMD Radeon 780M Graphics
Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU
Manufacturer: LENOVO
Product Name: 82XT
System Version: LOQ 15APH8

Maybe a log in the user journal?

Thanks, found the following:

Jun 25 22:32:09 aurora systemd[2317]: Started app-systemsettings@77d839c496a646159a5d6e9d9df09ef0.service - System Settings - System Settings.
Jun 25 22:32:09 aurora systemsettings[23544]: Failed to connect to Bolt manager DBus interface:
Jun 25 22:32:10 aurora systemsettings[23544]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, "Could not register app>
Jun 25 22:32:21 aurora hdrcalibrator[23625]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, "Could not register app >
Jun 25 22:32:27 aurora hdrcalibrator[23714]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, "Could not register app >
Jun 25 22:32:35 aurora hdrcalibrator[23769]: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, "Could not register app >
Jun 25 22:32:35 aurora kwin_wayland[2528]: Libinput: event10 - Newmen Tech.,LTD 2.4G Wireless Mouse: client bug: event processing lagging behind by 25ms, y>
– Boot 2dfdebd9bf534a5793f3d7534726965c –

Removing the wireless mouse as mentioned in the last line fixes the issue, not sure how these two correlate with each other!

A wild guess; the windows manager is also monitoring input devices.
If the mouse is not working well the window manager may hang and stop updating t(e screen.
But that is just a guess.