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
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
https://bugs.kde.org/show_bug.cgi?id=442520
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest
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.
https://bugs.kde.org/show_bug.cgi?id=442520
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #51 from Bug
https://bugs.kde.org/show_bug.cgi?id=442520
Nate Graham changed:
What|Removed |Added
CC||grouchomarx...@gmail.com
--- Comment #50 from
https://bugs.kde.org/show_bug.cgi?id=442520
Patrick Silva changed:
What|Removed |Added
CC||ka...@soltysik.net
--- Comment #49 from
https://bugs.kde.org/show_bug.cgi?id=442520
Marc Riedel changed:
What|Removed |Added
CC||m.riedel@gmail.com
--- Comment #48 from Marc
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
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
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] ->
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://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.
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.
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
https://bugs.kde.org/show_bug.cgi?id=442520
Méven Car changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
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.
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.
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
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.
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.
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
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
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
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
--
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
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
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
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
https://bugs.kde.org/show_bug.cgi?id=442520
p...@protonmail.com changed:
What|Removed |Added
CC||p...@protonmail.com
--- Comment #26 from
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:
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
https://bugs.kde.org/show_bug.cgi?id=442520
arun changed:
What|Removed |Added
CC||lunar.a...@gmail.com
--- Comment #23 from arun ---
I
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.
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
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
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
https://bugs.kde.org/show_bug.cgi?id=442520
Zamundaaa changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|1
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
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
https://bugs.kde.org/show_bug.cgi?id=442520
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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
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-0
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.
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 :/
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.
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
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-1
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
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.
https://bugs.kde.org/show_bug.cgi?id=442520
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #5 from Bug Janitor
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
52 matches
Mail list logo
