[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #55 from Marc Riedel --- Hi guys, the bug fix looks good. Running version 5.24.4 and didn't encountered this issue anymore. Also the RGB setting in kscreen settings menu gets remembered correctly. Thanks and best regards, Marc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwayland-server/commit/b |ma/kwayland-server/commit/a |90a3cbb4c3615fa6bf6dc8ffb57 |8e66dd1360624f9fef016598435 |47da7d5deb60|182d7faa635a --- Comment #54 from Nate Graham --- Git commit a8e66dd1360624f9fef016598435182d7faa635a by Nate Graham, on behalf of Xaver Hugl. Committed on 11/03/2022 at 16:14. Pushed by ngraham into branch 'Plasma/5.24'. outputchangeset: set default values for vrr policy and rgb range If this is not done then KScreen will sometimes unintentionally reset them to the default. FIXED-IN: 5.24.4 (cherry picked from commit b90a3cbb4c3615fa6bf6dc8ffb5747da7d5deb60) M +2-0src/server/outputchangeset_v2.cpp https://invent.kde.org/plasma/kwayland-server/commit/a8e66dd1360624f9fef016598435182d7faa635a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/libkscreen/commit/f659d8 |ma/kwayland-server/commit/b |8aaae2690207a39e7c60c7f2ecf |90a3cbb4c3615fa6bf6dc8ffb57 |3aedecb |47da7d5deb60 Version Fixed In||5.24.4 Resolution|--- |FIXED --- Comment #53 from Zamundaaa --- Git commit b90a3cbb4c3615fa6bf6dc8ffb5747da7d5deb60 by Xaver Hugl. Committed on 11/03/2022 at 02:51. Pushed by ngraham into branch 'master'. outputchangeset: set default values for vrr policy and rgb range If this is not done then KScreen will sometimes unintentionally reset them to the default. FIXED-IN: 5.24.4 M +2-0src/server/outputchangeset_v2.cpp https://invent.kde.org/plasma/kwayland-server/commit/b90a3cbb4c3615fa6bf6dc8ffb5747da7d5deb60 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #52 from Zamundaaa --- I managed to reproduce the bug, this MR should finally fix it for good. If someone else could verify that would be good though -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #51 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwayland-server/-/merge_requests/360 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Nate Graham changed: What|Removed |Added CC||grouchomarx...@gmail.com --- Comment #50 from Nate Graham --- *** Bug 450172 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Patrick Silva changed: What|Removed |Added CC||ka...@soltysik.net --- Comment #49 from Patrick Silva --- *** Bug 450029 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Marc Riedel changed: What|Removed |Added CC||m.riedel@gmail.com --- Comment #48 from Marc Riedel --- Hi guys, the behavior didn't change. After logout/login cycle, "rgbrange" stays "1" for the files in "kscreen/control/outputs" and "kscreen/control/configs" but not for the files in "kscreen" and in "kscreen/outputs". They are reverted to "0". Furthermore, the apply/discard prompt doesn't show up after hitting apply, so the settings are reverted after the timeout. When starting kscreen via kcmshell5, it works like it should. Tested with the latest release: Betriebssystem: Debian GNU/Linux KDE-Plasma-Version: 5.24.0 KDE-Frameworks-Version: 5.90.0 Qt-Version: 5.15.2 Kernel-Version: 5.16.0-7.slh.1-aptosid-amd64 (64-bit) Grafik-Plattform: Wayland Prozessoren: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Speicher: 31,2 GiB Arbeitsspeicher Grafikprozessor: Mesa DRI Intel® UHD Graphics 630 Best regards Marc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #47 from Méven Car --- Git commit d81b106c1554a36c14c55d81083268a79b057a91 by Méven Car, on behalf of Méven Car. Committed on 03/01/2022 at 15:40. Pushed by meven into branch 'master'. Apply the rgbrange read from Kscreen configuration on startup M +1-0src/abstract_wayland_output.cpp M +4-0src/backends/drm/drm_backend.cpp https://invent.kde.org/plasma/kwin/commit/d81b106c1554a36c14c55d81083268a79b057a91 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #46 from Méven Car --- In someone with the needed hardware could test the tentative kwin patch https://invent.kde.org/plasma/kwin/-/merge_requests/1830 This should make kwin restore your rgb range setting on startup. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #45 from Méven Car --- (In reply to Mrcuve0 from comment #42) > Created attachment 144959 [details] > Mrcuve0 - kscreen_terminal.log Great, this confirms the issue is on Kscreen side: [4081578,804] -> kde_output_management_v2@49.create_configuration(new id kde_output_configuration_v2@55) [4081578,967] -> kde_output_configuration...@55.mode(kde_output_device_v2@50, kde_output_device_mode_v2@4278190082) [4081579,040] -> kde_output_configuration...@55.mode(kde_output_device_v2@51, kde_output_device_mode_v2@4278190115) [4081579,063] -> kde_output_configuration_v2@55.set_rgb_range(kde_output_device_v2@51, 1) [4081579,098] -> kde_output_configuration_v2@55.apply() [...] [4081635,736] kde_output_device_v2@51.rgb_range(1) [4081635,782] kde_output_device...@51.done() [4081635,815] kde_output_configuration_v2@55.applied() -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #44 from Mrcuve0 --- Just to add additional information to my setup, some days ago I wanted to try OC my screens to 75Hz "for the lulz" following https://old.reddit.com/r/linux_gaming/comments/e339il/how_to_overclock_your_monitor_on_wayland/. Hence why you'll find 75Hz in the configs and logs. It probably does not have effects on the bug but, you know, sometimes "very unlikely" configs have an impact on what you are trying to debug and you find it only after hours of wasted time -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #43 from Mrcuve0 --- Created attachment 144960 --> https://bugs.kde.org/attachment.cgi?id=144960=edit Mrcuve0 - kscreen.log (.local/share/kscreen/) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #42 from Mrcuve0 --- Created attachment 144959 --> https://bugs.kde.org/attachment.cgi?id=144959=edit Mrcuve0 - kscreen_terminal.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #41 from Mrcuve0 --- I'm adding two different logs: * The first one `kscreen_terminal.log` is the one you asked (I'd like to understand why redirecting with tee or > didn't work with this particular command, anyway I copy pasted the stdout to this file :D). * The second one `kscreen.log` is the one produced by setting the .sh file in plasma-workspace/env like https://community.kde.org/Solid/Projects/ScreenManagement suggests. Hope both help. Anyway, I quickly searched for the string you mentioned and couldn't see it. It is also woth mentioning that both screens (e-DP1, my laptop's builtin, and DP-1 Dell U2419HC, my external one) were set to "automatic" before launching the command. However, DP-1 was clearly showing a "full-RGB" image. I tried to restart and disconnect DP-1 multiple times while having "automatic" in kscreen to force it to a visually "limited" scale but I couldn't. Also closing the laptop lid didn't change anything. It's interesting because some months ago (at least as soon as i got 5.23 on tumbleweed) these operations would have triggered the bug instantly (i.e. DP-1 would clearly show a "limited" image), now I cannot find a way to reproduce it sistematically (but I can guarantee you that I still have to manually launch kscreen just to set to "full" DP-1 from time to time) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Méven Car changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #40 from Méven Car --- (In reply to Mrcuve0 from comment #39) > Created attachment 144937 [details] > Mrcuve0 - kscreen folder Thanks for those folders. Your two configs have `"rgbrange": 0,` (automatic) in common, it should be `"rgbrange": 1,` for Full. It seems to indicate kscreen kded did not save the rgb range correctly, or KWin did not transmit it. So a great thing that can help is to be in a automatic state, run `WAYLAND_DEBUG=1 kcmshell5 kscreen`, keep the output, (this is quite verbose). Then switch to full. We should see in the trace a `output_devicev2.send_rgb_range(1)` or similar after the activation, if not the bug is in KWin side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #39 from Mrcuve0 --- Created attachment 144937 --> https://bugs.kde.org/attachment.cgi?id=144937=edit Mrcuve0 - kscreen folder -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #38 from Patrick Silva --- Created attachment 144933 --> https://bugs.kde.org/attachment.cgi?id=144933=edit my ~/.local/share/kscreen folder -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #37 from Méven Car --- Could you share the folder ~/.local/share/kscreen content -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #36 from Zamundaaa --- *** Bug 446617 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #35 from Zamundaaa --- Thanks for the investigation, the bug is almost certainly in KScreen then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #34 from Mrcuve0 --- I added "export QT_LOGGING_RULES="kwin_*.debug=true" as suggested, removed the log and rebooted to reach a clean state. I recorded 4 different logs for the 4 subsequent actions done: * 00a: shows the initial state of the log, the screen is on Automatic and no preference has been set yet * 00b: the log records the instant when I switch from Automatic to Full, before logout *** LOGOUT *** * 01a: shows the state after logout, the screen is back in Automatic mode * 01b: I switch again from Automatic to Full, the log records this action Points of Interest I noticed using diff: --> Comparison among 00b and 01a (logout happens in between): * Line 7: The properties of Crtc 60 change (why?) * Line 70: The properties of connector 77 change (why?) * Line 71: Connector 85 (crtc 60) goes from Automatic to Full * Line 74 and 75: The two hex addresses changes (IDs?) * Line 421 in 01a sets the RGB range to Automatic --> Comparison among 01a and 01b: * Line 522: the RGB range is set to Full --- I didn't find any "kwin_wayland_drm: Atomic test for (0) failed! Invalid argument" string in these logs, however we can find on line 4: "kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card0" So I guess the error does not produce in my case (?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #33 from Mrcuve0 --- Created attachment 142673 --> https://bugs.kde.org/attachment.cgi?id=142673=edit After logout, Automatic to Full After logout, I switch again from Automatic to Full, the logs records this action -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #32 from Mrcuve0 --- Created attachment 142672 --> https://bugs.kde.org/attachment.cgi?id=142672=edit After Logout The logs shows the state after logout/login -> the screen is back to Automatic RGB mode -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #31 from Mrcuve0 --- Created attachment 142671 --> https://bugs.kde.org/attachment.cgi?id=142671=edit Before Logout, Atuomatic -> Full The logs records the instant where I change RGB mode from Automatic to Full, before logging out -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #30 from Mrcuve0 --- Created attachment 142670 --> https://bugs.kde.org/attachment.cgi?id=142670=edit Before Logout, initial state of the log Before Logout, the screen is already in Automatic RGB mode, initial state of the log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #29 from Zamundaaa --- Either set it like this for your user account: https://invent.kde.org/plasma/kwin/-/wikis/Environment-Variables#usage or put it in /etc/environment to set it globally When you have that, set rgb range to something else than automatic, log out, log in and have a look at the session log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #28 from p...@protonmail.com --- > Can you check for "Atomic test for (0) failed!" in > ~/.local/sddm/wayland-session.log? I just read your second comment and I believe I don't have debug logging enabled, can you tell me how can I enable it? Sorry noob here. I tried adding "export QT_LOGGING_RULES="kwin_*.debug=true" to my .bashrc, logout, and then launch "systemsettings5 kcm_kscreen" but I can't see any additional info added to the logfile -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #27 from Zamundaaa --- Can you check for "Atomic test for (0) failed!" in ~/.local/sddm/wayland-session.log? I don't have a device that supports it and faking support in KWin still seems to make it work fine, maybe there's something with driver interaction that makes it fail. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 p...@protonmail.com changed: What|Removed |Added CC||p...@protonmail.com --- Comment #26 from p...@protonmail.com --- Can confirm, on Opensuse TW w/ 5.23 I'm having the exact same issue as pointed out by Patrick Silva. I was going to file a bug for the case and discovered this one instead. To better define my environment: I have two monitors, my FHD laptop on the left and my secondary FHD screen on the right, which is also the "main" one (although no such definition exists on wayland yet). My secondary monitor, when RGB Range is on "automatic" is actually set on "limited" (although it should refer to "full" as it is perfectly capable to do such setting). I noticed that whenever I force "Full" (no matter for which screen and no matter the "Save display's properties" setting below), if I disconnect my secondary screen on the right and reconnect it, all the setting (even those related to the laptop screen) revert to "automatic". Hence, my secondary screen reverts to a limited RGB range, which is quite annoying now that I discovered my monitor does not have washed out colors ahaha. Laptop screen: Dell XPS 13 9343 Secondary screen: Dell U2419HC Let me know if I can attach further information/logs etc! Operating System: openSUSE Tumbleweed 20211016 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 7,7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #25 from Patrick Silva --- RGB range is reverted to "Automatic" affer re-login on Plasma 5.23 too. "Automatic" means "Limited" on my system. Operating System: Arch Linux KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #24 from Zamundaaa --- You need up to date builts of the Plasma/5.23 branch (or git master) for libkscreen, kscreen, kwayland-server and kwin, the single patch won't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 arun changed: What|Removed |Added CC||lunar.a...@gmail.com --- Comment #23 from arun --- I have this issue. I have tried patching with mr 44. still it doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #22 from Zamundaaa --- I can't reproduce the logout+login problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #21 from Zamundaaa --- Git commit c2180098a5646a8d2e48c5eb6aec99fcf9e88ec4 by Xaver Hugl. Committed on 22/09/2021 at 17:22. Pushed by zamundaaa into branch 'Plasma/5.23'. fix all the new settings There were still bits missing for the global config (cherry picked from commit 38c258a1d7b007281ffae4f67621491378d0f4aa) M +18 -1kded/output.cpp M +3-0kded/output.h https://invent.kde.org/plasma/kscreen/commit/c2180098a5646a8d2e48c5eb6aec99fcf9e88ec4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #20 from Zamundaaa --- Git commit 38c258a1d7b007281ffae4f67621491378d0f4aa by Xaver Hugl. Committed on 22/09/2021 at 17:21. Pushed by zamundaaa into branch 'master'. fix all the new settings There were still bits missing for the global config M +18 -1kded/output.cpp M +3-0kded/output.h https://invent.kde.org/plasma/kscreen/commit/38c258a1d7b007281ffae4f67621491378d0f4aa -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #19 from Patrick Silva --- (In reply to Zamundaaa from comment #18) > Ack, it doesn't work with global retention. Can you try > https://invent.kde.org/plasma/kscreen/-/merge_requests/44? Applied your patch. Full rgb range is preserved after reboot, but it is not after re-login. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Zamundaaa changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #18 from Zamundaaa --- Ack, it doesn't work with global retention. Can you try https://invent.kde.org/plasma/kscreen/-/merge_requests/44? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520
--- Comment #17 from Patrick Silva ---
I have built 5.23 branch of libkscreen, kwayland-server, kwin, kscreen
and plasma-workspace. But rgb range is still reverted to limited
("Automatic" is selected in KCM) after re-login.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/libkscreen/commit/b6f7e1 |ma/libkscreen/commit/f659d8 |627104bb6dc811374e92d108853 |8aaae2690207a39e7c60c7f2ecf |0c3d1ae |3aedecb --- Comment #16 from Zamundaaa --- Git commit f659d88aaae2690207a39e7c60c7f2ecf3aedecb by Xaver Hugl. Committed on 21/09/2021 at 12:13. Pushed by zamundaaa into branch 'Plasma/5.23'. fix all the new settings While they were written to the control file, they were not written into the configuration files from kded and were thus reset after a session restart (cherry picked from commit b6f7e1627104bb6dc811374e92d1088530c3d1ae) M +20 -5src/output.cpp M +3-3src/output.h https://invent.kde.org/plasma/libkscreen/commit/f659d88aaae2690207a39e7c60c7f2ecf3aedecb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/libkscreen/commit/b6f7e1 ||627104bb6dc811374e92d108853 ||0c3d1ae --- Comment #15 from Zamundaaa --- Git commit b6f7e1627104bb6dc811374e92d1088530c3d1ae by Xaver Hugl. Committed on 21/09/2021 at 11:31. Pushed by zamundaaa into branch 'master'. fix all the new settings While they were written to the control file, they were not written into the configuration files from kded and were thus reset after a session restart M +20 -5src/output.cpp M +3-3src/output.h https://invent.kde.org/plasma/libkscreen/commit/b6f7e1627104bb6dc811374e92d1088530c3d1ae -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #14 from Zamundaaa --- Git commit 4008dccebc51f79a283852399a778c4d546c8dd8 by Xaver Hugl. Committed on 21/09/2021 at 12:12. Pushed by zamundaaa into branch 'Plasma/5.23'. outputdevice: add missing done events (cherry picked from commit 67e629aa18ba878d4f3566457b6fbfff7ec949fd) M +8-0src/server/outputdevice_v2_interface.cpp https://invent.kde.org/plasma/kwayland-server/commit/4008dccebc51f79a283852399a778c4d546c8dd8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #13 from Zamundaaa --- Git commit 67e629aa18ba878d4f3566457b6fbfff7ec949fd by Xaver Hugl. Committed on 21/09/2021 at 11:34. Pushed by vladz into branch 'master'. outputdevice: add missing done events M +8-0src/server/outputdevice_v2_interface.cpp https://invent.kde.org/plasma/kwayland-server/commit/67e629aa18ba878d4f3566457b6fbfff7ec949fd -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #12 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libkscreen/-/merge_requests/34 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #11 from Zamundaaa --- The bug as per the first description should be fixed but the setting is not restored by kded, even though it is saved into the config file(s). I must've overlooked something in KScreen. Too much boilerplate code :/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #10 from Nate Graham --- Anything more to do here, or should this be fixed now? Can you test, Patrick? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #9 from Zamundaaa --- Git commit 6455499dca1b589d87184ef128bd9b226899f8ce by Xaver Hugl. Committed on 17/09/2021 at 13:56. Pushed by zamundaaa into branch 'Plasma/5.23'. platforms/drm: allow modesets when setting Broadcast RGB (cherry picked from commit 4848964c6036803b5fa0d88340960b44a113da67) M +5-1src/plugins/platforms/drm/drm_object_connector.cpp https://invent.kde.org/plasma/kwin/commit/6455499dca1b589d87184ef128bd9b226899f8ce -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #8 from Zamundaaa --- Git commit 4848964c6036803b5fa0d88340960b44a113da67 by Xaver Hugl. Committed on 17/09/2021 at 13:48. Pushed by zamundaaa into branch 'master'. platforms/drm: allow modesets when setting Broadcast RGB M +5-1src/plugins/platforms/drm/drm_object_connector.cpp https://invent.kde.org/plasma/kwin/commit/4848964c6036803b5fa0d88340960b44a113da67 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #7 from Patrick Silva --- (In reply to Zamundaaa from comment #6) > Can you test the patch? I have applied your patch to my system. Now I can apply full rgb range but it is reverted to limited when I restart Plasma session. And when I apply full rgb range and then immediately reopen the KCM, rgb range combobox is empty or Automatic option is selected. These issues persist after reboot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #6 from Zamundaaa --- Can you test the patch? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1426 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 Zamundaaa changed: What|Removed |Added Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org Product|systemsettings |kwin Component|kcm_kscreen |platform-drm --- Comment #4 from Zamundaaa --- Okay, thanks. I have an idea about what could be causing this -- You are receiving this mail because: You are watching all bug changes.
