User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0 Build Identifier: Timezones are broken, see https://gitlab.gnome.org/GNOME/glib/-/issues/2224. Reproducible: Always
Proposed as a Freeze Exception for 33-final by Fedora user catanzaro using the blocker tracking app because: Top bar time is incorrect, timezone map in control center is broken... general basic functionality failure in apps that use glib.
(In reply to Michael Catanzaro from comment #0) > Timezones are broken, see https://gitlab.gnome.org/GNOME/glib/-/issues/2224. Also https://gitlab.gnome.org/GNOME/glib/-/issues/2215. Two for one!
2215 seems to be a Windows-specific bug? 2224 looks worrying, but...doesn't provide any info on the context in which this happens. When does the bug happen? To everyone all the time? I mean, my top bar time looks right, right now...with glib2-2.66.1-1.fc33.x86_64...was this introduced by something newer?
(In reply to Adam Williamson from comment #3) > 2215 seems to be a Windows-specific bug? Well that caused a lot of confusion, but no, it seems to be affecting Linux too. I think the Windows users just assumed that glib wouldn't have a bug this serious on Linux :P > 2224 looks worrying, but...doesn't provide any info on the context in which > this happens. When does the bug happen? To everyone all the time? I mean, my > top bar time looks right, right now...with glib2-2.66.1-1.fc33.x86_64...was > this introduced by something newer? It makes changing timezone impossible once a process starts. So if you open up gnome-control-center and try to change the timezone, you'll notice that panel is broken: https://gitlab.gnome.org/GNOME/glib/-/issues/2224#note_934734. Chris was having some trouble related to automatic timezone changing the timezone as well, not sure about the full details there.
Thanks for the details.
I discovered this independently of the existing reports. It's been closed, but has screenshots that help clarify the visual manifestation of the bug. https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/174
FEDORA-2020-a5131d7862 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a5131d7862
(In reply to Chris Murphy from comment #6) > It's been closed, It's just moved to a different component. If you click on the blue "Closed (moved)" label it will take you to the open bug. There's also some fine print in the issue history you can use to get to the open issue.
+5 votes in https://pagure.io/fedora-qa/blocker-review/issue/174 , marking accepted.
FEDORA-2020-a5131d7862 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a5131d7862` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a5131d7862 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-a5131d7862 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.