[nvidia] [radeon] Shell labels randomly disappear from the menu panel (top bar)

[Tom]

Description: Ubuntu 20.04.1 LTS
Release: 20.04

gnome-shell:
  Installed: 3.36.4-1ubuntu1~20.04.2
  Candidate: 3.36.4-1ubuntu1~20.04.2
  Version table:
 *** 3.36.4-1ubuntu1~20.04.2 500
        500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     3.36.1-5ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

Feb 1 22:09:05 tomsfastbox systemd[1]: Finished Clean php session files.
Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Qt: Failed to create XKB context!
Feb 1 22:09:23 tomsfastbox multipass.gui.autostart.desktop[3949]: [2021-02-01T22:09:23.440] [warning] [Qt] Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ .
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Feb 1 22:09:23 tomsfastbox gnome-shell[3626]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Feb 1 22:09:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 1 22:10:32 tomsfastbox systemd-resolved[918]: message repeated 13 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.]
Feb 1 22:11:19 tomsfastbox gnome-shell[3626]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
Feb 1 22:11:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 1 22:12:32 tomsfastbox systemd-resolved[918]: message repeated 14 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.]
Feb 1 22:12:49 tomsfastbox gnome-shell[3626]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5000007
Feb 1 22:13:32 tomsfastbox systemd-resolved[918]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

I'm also using a StreamDeck USB device, if that's useful.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 1 22:16:07 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-18 (290 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-07-10 (206 days ago)

[Daniel van Vugt (vanvugt)]

1. It looks like ubuntu-appindicators is active on this machine. Are you sure it's not just indicator icons covering the clock, like bug 1883130?

2. Please also provide a screenshot or photo of the problem.

3. You seem to have the nvidia driver installed, which may also be the problem if the labels go missing after resume from suspend/hibernate (bug 1876632). Please check to see if the problem only occurs after suspend/resume or VT switching.

[Tom (tomammon)]

1. I don't think something is covering the clock, because it's not just the clock that has problems. The text on other controls on menu panel is also affected, see attached photos.

2. Attached

3. bug 1876632 seems similar, however the text is not corrupted, it has simply disappeared.

[Tom (tomammon)]

Additional screenshot attached

[Daniel van Vugt (vanvugt)]

Thanks. Next please run:

  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

[Daniel van Vugt (vanvugt)]

Please also check to see if the problem only occurs after suspend/resume or VT switching.

[Tom (tomammon)]

This is a desktop computer so I don't suspend and resume. However I do lock the screen regularly, but I could not reproduce the problem by locking and unlocking the screen.

The problem seems to occur after a certain amount of uptime, though I have not measured how much uptime.

Requested output attached.

[Daniel van Vugt (vanvugt)]

Thanks. It's possible there's some VT switching happening in the screen locking/unlocking. Or just mode switching. If so then that can trigger an annoying feature of the Nvidia driver where it will forget its textures:

https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

We don't yet have all the fixes we need to deal with that feature of Nvidia, and it can't be turned off either. The other bugs associated with this are bug 1876632 and bug 1855757.

There's also bug 1910435 which sounds most similar to this, but the author of that bug is not responding at the moment.

[Daniel van Vugt (vanvugt)]

Actually I might have been too quick to blame Nvidia. Let's group this with bug 1910938 until proven otherwise.