Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64087 - [gnome] night light broken in gnome 3.34.1

Attached to Project: Community Packages
Opened by Carlo Carloni Calame (cmcc) - Thursday, 10 October 2019, 09:11 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 03 November 2019, 11:37 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 14
Private No

Details

As reported here
https://bbs.archlinux.org/viewtopic.php?id=249805
night light mode is broken (on wayland) in latest gnome. I'm not sure which gnome component is to blame (gnome-shell, gnome-session, gnome-control-center, gnome-settings-daemon, colord?)

Description:
Night light mode won't start, even if in gnome-control-center it is correclty configured and activated.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Sunday, 03 November 2019, 11:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  mutter 3.34.1+12+g943b06999-1
Comment by Andrea (Dea1993) - Thursday, 10 October 2019, 17:16 GMT
i can confirm the issue.
after upgrading gnome to 3.34.1 night light no more works.
on gnome panel the icon of night light appears, but the screen temperature doesn't change.
this problem happends only on wayland, instead on Xorg it works perfectly
Comment by Carlo Carloni Calame (cmcc) - Thursday, 10 October 2019, 18:26 GMT
I must say that now night light works again (on wayland). I'm confused, I didn't know where the issue came from and now I don't know where it disappeared :D. Since yesterday I rebooted once my laptop.
Please confirm if it's working again, so we can close the bug.
Comment by Andrea (Dea1993) - Thursday, 10 October 2019, 19:38 GMT
i've this problem from yesterday after gnome shell update, and i still have this problem also todat after reboot.
instead on xorg it's ok
Comment by Amr (dr3mro) - Friday, 11 October 2019, 01:08 GMT
I confirm this to using arch linux with wayland server
Comment by Shane (s) - Monday, 14 October 2019, 04:24 GMT
I'm also affected by this issue.

It looks like its fixed upstream in Mutter 3.35.1.
Annoucement: https://mail.gnome.org/archives/gnome-announce-list/2019-October/msg00009.html
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/851
Comment by Ruud van Asseldonk (ruudva) - Monday, 14 October 2019, 19:12 GMT
As a workaround, downgrading the `mutter` package to 3.34.0+30+gb5775e3d8-1 resolved the issue for me. So far I haven’t run into any compatibility issues with the rest of Gnome 3.34.1. Thanks Shane, for pointing out that the bug is in Mutter.
Comment by Dominik Fischer (XZS) - Monday, 14 October 2019, 22:35 GMT
I assumed an early upgrade is better than a downgrade, so I tried it out with the mutter version 3.34.1+12+g943b06999-1 currently available in the testing repository. This fixed it for me. So I also like to thank you for your finding.
Comment by Jad Tala (NotNeo) - Wednesday, 16 October 2019, 19:29 GMT
I'm affected by this issue on Wayland, even color profiles are broken, I can't adjust my OLED monitor's brightness using icc-brightness anymore. Everything works perfectly on Xorg though.
Comment by Jad Tala (NotNeo) - Wednesday, 16 October 2019, 19:43 GMT
I can confirm upgrading mutter to the version 3.34.1+12+g943b06999-1 from the testing repository fixes the issue, thank you for pointing that out.

Loading...