Created attachment 165045 [details] The output of "kscreen-console bug" SUMMARY The configuration of the Display & Monitor System Setting page don't persist after shutdown or logout. This only apply to the RC1 and master branch, but not on the 5.27 release (but i'm not sure that is not a problem with some other newer dependencies). STEPS TO REPRODUCE 1. Change some setting in Display & Monitor System Setting page (ex. scale factor) 2. Apply settings 3. Reboot OBSERVED RESULT The setting are reset to the default value. EXPECTED RESULT The setting persist a reboot. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 Kernel Version: 6.7.0-arch3-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics Memory: 14,9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming A15 FA507NV_FA507NV System Version: 1.0 ADDITIONAL INFORMATION This only happen on my primary machine while my secondary machine (even with same install) is unaffected.
Created attachment 165046 [details] Warning and error of journal of boot Possible usefull error are gen 19 07:22:24 arch kwin_wayland[1236]: kwin_core: Duplicate output found in config for edidIdentifier: "<empty>" ; connectorName: "eDP-1" ; mstPath: "" gen 19 07:22:24 arch kwin_wayland[1236]: kwin_core: parsing edid failed gen 19 07:22:24 arch kwin_wayland[1236]: kwin_wayland_drm: Couldn't parse EDID for connector DrmConnector(id=93, gpu=KWin::DrmGpu(0x5c1ac87db5c0), name="eDP-1-unknown", connection="Connected", countMode=14) gen 19 07:22:24 arch kwin_wayland[1236]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
EDID parsins was just improved today with https://invent.kde.org/plasma/kwin/-/commit/d563bc6c86d398a59409f5ea1ad556d93fb45f78, in fact; can you update to the latest version in a few days so that you get that commit, and try again?
Just updated my build to today master branch and there the bug is resolved.
Excellent news!