Bug 1888937 - Clock in center top panel out of sync with date command
Summary: Clock in center top panel out of sync with date command
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-16 12:29 UTC by Kevin Raymond
Modified: 2021-11-30 16:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:44:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Raymond 2020-10-16 12:29:30 UTC
Description of problem:
Since I upgraded from F31 to F33 (alpha then beta) I can see several times a week my gnome-shell clock behind the real time by... Several minutes or even 1h. It is not a timezone issue.
However, at some point, the clock just move forward to the right time.
At first I expected a chrony/NTP server issues, however I just saw that the "date" commande is in sync and right.

It might be the gnome-shell clock not being updated after fullsreen application or "screensaver"

Version-Release number of selected component (if applicable):
gnome-shell-3.38.0-2.fc33.x86_64

How reproducible:
Not sur how to reproduce yet I just spotted that the issue might be in gnome-shell. 

Steps to Reproduce:
1. Read the clock and compare to your next meeting time
2. Go make a coffee
3. Third coffee and still plenty of time? Check time on your wall clock… Alright, something is going wrong
4. The gnome-shell clock update to the right time "at some point" (at least several seconds to few minutes?)

I'll try to check is this issue is "screen activity" related

Actual results:
gnome-shell clock is behind the system clock

Expected results:
gnome-shell clock in sync with the system clock

Additional info:
I don't see any useful log
The clock is set as "network time" under the gnome setting panel.

I already got this kind of bug. Might be related to https://bugzilla.gnome.org/show_bug.cgi?id=635840

Comment 1 Kevin Raymond 2020-10-20 11:44:58 UTC
I can reproduce having my web browser full screen, after several minutes quit the full screen mode. The gnome-shell clocks is out to date.
However, it goes forward to the real time once it is refreshing  (at every least 59 seconds)

Comment 2 tsroeirl 2020-11-07 15:08:01 UTC
I can confirm that the wall clock is not updated, when an application like Firefox is in full screen mode and one presses the super-key to view the Gnome overview or one exits the full screen mode after some time. Hovering with mouse over the unsynchronized clock synchronizes it to the right time.

Comment 3 Jonas Ådahl 2020-11-07 16:39:42 UTC
Could be https://gitlab.gnome.org/GNOME/glib/-/issues/2224.

Comment 4 tsroeirl 2020-11-07 17:54:54 UTC
@(In reply to Jonas Ådahl from comment #3)
> Could be https://gitlab.gnome.org/GNOME/glib/-/issues/2224.

I don‘t think so, as in the linked bug the clock time is ahead of the real time by a constant time span while with my experience (and I think also with that of Raymond‘s), the clock stops at the time the full screen mode has been started.

Comment 5 Kevin Raymond 2020-11-10 10:03:17 UTC
GNOME issue here https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3350

Comment 6 Gregory Lee Bartholomew 2020-11-11 16:39:46 UTC
The GNOME issue linked in comment #5 appears to suggest that the clock will sync back up on the minute. However, I saw it out of sync by at least 10 minutes this morning when I had chrome, terminal, and hexchat running. I had gnome terminal running in full-screen mode, but it was in the background. Chrome and hexchat were maximized and I was tabbing between them. The clock was not refreshing (I was almost late to an IRC meeting because the clock was not advancing).

Comment 7 Kevin Raymond 2020-11-17 07:57:18 UTC
looks like the fix is shipped in 3.38.2  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2973
I don't know when this release is going to reach update-testing

Comment 8 Ben Cotton 2021-11-04 17:14:38 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2021-11-30 16:44:47 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.