I’m experiencing a similar issue. I’m new as far as snaps go, although I feel like this is a symptom of sandboxing.
EDIT: A key note is that I’m running on X11 - Could this be the case where the XSETTINGS isn’t set up properly to get the default cursor?
I’m running chromium version 81.0.4044.138 on xubuntu 20.04, the snap version I’m using described here:
λ snap info chromium
summary: Chromium web browser, open-source version of Chrome
An open-source browser project that aims to build a safer, faster, and more stable way for all
Internet users to experience the web.
refresh-date: 2 days ago, at 17:20 EDT
latest/stable: 81.0.4044.138 2020-05-06 (1143) 161MB -
latest/candidate: 81.0.4044.138 2020-05-06 (1143) 161MB -
latest/beta: 83.0.4103.44 2020-05-08 (1144) 163MB -
latest/edge: 84.0.4128.3 2020-04-29 (1136) 164MB -
installed: 81.0.4044.138 (1143) 161MB -
The connections listed includes the gtk-common-themes slot:
λ snap connections chromium
Interface Plug Slot Notes
content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes -
content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes -
Although I get the default X11 cursor when hovering over the instance.
This may be the wrong spot to poke to get the right answer. Is the case that the latest/stable branch doesn’t implement the
gtk-3-themes extension yet, even though the proper connections are listed? Is there a case where the snap makes a connection to the
gtk-common-themes extension but does not make use of it?