| Summary: | KDE Night Color broken due to Nvidia autostart command | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Elias <supgesu> |
| Component: | nvidia-settings | Assignee: | Nicolas Chauvet <kwizart> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | leigh123linux |
| Priority: | P1 | ||
| Version: | f37 | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
Elias
2022-12-20 21:11:49 CET
It works as appropriate with gnome "night mode" with me. (unless I run nvidia-settings directly). You might need to report this issue to nvidia. (and/or KDE desktop team). Just tested on my Gnome install. The load config command does also break Night Light on Gnome. However for some reason when leaving Night Light enabled in Gnome and re-login it stays on and working. Maybe the autostart entry doesn't run, or runs too early to have an effect on Night Light on Gnome? Not sure. But manually running `nvidia-settings -l` does reset the colors every time, also on Gnome. Independent of DEs, just questioning: Is this autostart command even still needed? Since I removed it I didn't notice any downsides. But maybe this is just on my setup. (In reply to Elias from comment #2) > Independent of DEs, just questioning: > Is this autostart command even still needed? Since I removed it I didn't > notice any downsides. But maybe this is just on my setup. Without autostart nvidia-settings wont apply Xorg settings. @Elias, Do you have a KDE report for the issue. KDE dev will have better insight to talk to nvidia than we do. It's not possible for us to disable this settings Closing the bug, please report any KDE/nvidia reports here for reference. (In reply to Nicolas Chauvet from comment #4) > @Elias, > > Do you have a KDE report for the issue. KDE dev will have better insight to > talk to nvidia than we do. It's not possible for us to disable this settings > > > Closing the bug, please report any KDE/nvidia reports here for reference. Hi, I found this KDE bug report: https://bugs.kde.org/show_bug.cgi?id=450288 I'm not 100% sure yet if this is the exact problem I'm seeing since I never experienced this on any other machines, only the one which is on Fedora + Nvidia currently. Not sure yet what the exact full cause is. But the bug report seems similar enough, so I also posted over there and shared a workaround for now. |