https://bugs.kde.org/show_bug.cgi?id=453070
Robert Britton <britto...@protonmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |britto...@protonmail.com
--- Comment #3 from Robert Britton <britto...@protonmail.com> ---
I can third this issue. Like Behzad -- Night Color works just fine on X11, but
it's completely broken on Wayland. I'm on Arch with a fully up-to-date system
as of today 5/1.
I can't say whether or not this happened before the current version of Plasma
I'm on was released into Arch repositories; I've only started trying to use
Wayland in the past week.
Night Color doesn't work whatsoever for me on Wayland. It doesn't matter what
activation time you set it to or what temperature you set it to adjust to, it
just doesn't work. It's as if it doesn't exist. The Night Color widget can be
toggled on or off, and it displays changes as such, but nothing happens.
I AM NOT A DEVELOPER but from my troubleshooting I think this might have to do
with the way monitor names are detected and tracked in Wayland versus X11. The
other major issue with Wayland I've been having is that on my current user
account, existing since January and whatever version of Plasma was available on
Arch then, any changes I make to display settings don't get saved, either
resolution or refresh rate. This means I have to re-set my monitor to output at
144 Hz every single time I start a Wayland session. I've tested pretty
extensively with a test user I made this weekend, and that user doesn't have
the settings-not-being-saved issue, but it does also have a broken Night Color.
I use a single monitor with DVI. I think these two issues may possibly be
related somehow.
System info:
Operating System: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 running proprietary
driver version 510.60.02
I'd be happy to provide more info if needed -- config files, etc.
--
You are receiving this mail because:
You are watching all bug changes.
