You are not logged in.
Hey,
I've recently noticed my gnome-shell clock (the one that is seen in the top bar) getting stuck: it shows the same time for multiple minutes. It eventually updates to the correct time.
Before I go ahead and file a bug report on the gnome gitlab, I wanted to ask if anyone here has an idea for how I could further investigate. I haven't been able to reproduce the bug. Logs have events for times when the gnome clock was stuck, so the issue doesn't seem to affect the system clock. The logs given by journalctl when the freeze starts (17:01):
Oct 18 17:05:41 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001d4.
Oct 18 17:05:38 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001cd.
Oct 18 17:01:07 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001c5.
Oct 18 17:00:55 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001bb.
Oct 18 17:00:55 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001b7.
Oct 18 17:00:55 lehto rtkit-daemon[712]: Supervising 6 threads of 4 processes of 1 users.
Oct 18 17:00:55 lehto rtkit-daemon[712]: Supervising 6 threads of 4 processes of 1 users.
Oct 18 17:00:50 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001b0.
Oct 18 17:00:41 lehto gnome-shell[857]: libinput error: event4 - AT Translated Set 2 keyboard: client bug: event processing lagging behind by 11ms, your system is too slow
Oct 18 17:00:26 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001a8.
Oct 18 17:00:18 lehto gnome-shell[857]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1600008 specified for 0x16001a1.
Oct 18 17:00:08 lehto wpa_supplicant[517]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-59 noise=9999 txrate=173300and when it ends (17:18)
Oct 18 17:18:07 lehto rtkit-daemon[712]: Supervising 5 threads of 3 processes of 1 users.
Oct 18 17:18:07 lehto rtkit-daemon[712]: Supervising 5 threads of 3 processes of 1 users.
Oct 18 17:18:06 lehto rtkit-daemon[712]: Supervising 5 threads of 3 processes of 1 users.
Oct 18 17:18:06 lehto rtkit-daemon[712]: Supervising 5 threads of 3 processes of 1 users.
Oct 18 17:17:11 lehto gnome-shell[857]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x180000e
Oct 18 17:17:11 lehto systemd[772]: Started Application launched by gsd-media-keys.Last edited by hagfish (2020-10-20 17:05:30)
Offline
Hello,
Your issue looks similar to this bug report: https://gitlab.gnome.org/GNOME/gnome-sh … ssues/2973
A fix was committed today on the Mutter master branch ![]()
I had the same issue after watching a fullscreen movie with VLC when returning to the shell.
Last edited by Spike29 (2020-10-20 17:00:44)
Offline
I just noticed similar issue yesterday. Looks like I can reproduce with fullscreen windows (at least mpv and firefox fullscreen video seem to trigger this). However, at least in my case, the clock updates when I move the mouse cursor over it. It may be worth noting that I only tested this on wayland so far.
If you can reproduce this with full screen windows as well, I think that should be good enough lead for the bug report.
Also, I don't think there's anything on your journal logs is related to this. If we are experiencing the same issue, this seems to be some widget redrawing issue within gnome-shell, that shouldn't produce any errors.
EDIT. Looks like this would be the issue mentioned by Spike29 above, and should be fixed also in the gnome-shell 3.38 branch since today.
Last edited by ooo (2020-10-20 17:07:52)
Offline
Ah, I didn't think to use "update" as a search term. This does indeed look like the same issue. Thank you, it's nice to know the problem is being taken care of
.
Offline