Thanks to the pointer. I now have 3.30.1-2ubuntu1.18.10.2 and it seems the issue is resolved (not sure if this is the new version or the manual fix below, which I applied thanks to your pointer).
I'd installed the Pop theme manually (through apt) atop stock 18.10. The slightly unorthodox thing I'd done was a soft-link from /usr/share/gnome-shell/theme/Yaru/gnome-shell.css onto ../gnome-shell.css, which is itself a soft-link to /usr/share/themes/Pop/gnome-shell/gnome-shell.css This would consistent theming of the lock screen, which doesn't appear to obey the control panel setting. Using the soft-links also makes it easier to spot when those files get overwritten by updates.
So it looks like the changes introduced in 3.30.1-2ubuntu1.18.10.1 makes it impossible to follow symlinks from /usr/share/gnome-shell/theme/Yaru/gnome-shell.css ? I guess it's perhaps debatable whether the standard gnome-shell package should reference a hardcoded theme (or maybe that's a GNOME limitation?)
Anyway, since I've worked around this issue, I guess this bug can be closed.
Hi Daniel,
Thanks to the pointer. I now have 3.30.1- 2ubuntu1. 18.10.2 and it seems the issue is resolved (not sure if this is the new version or the manual fix below, which I applied thanks to your pointer).
I'd installed the Pop theme manually (through apt) atop stock 18.10. The slightly unorthodox thing I'd done was a soft-link from /usr/share/ gnome-shell/ theme/Yaru/ gnome-shell. css onto ../gnome-shell.css, which is itself a soft-link to /usr/share/ themes/ Pop/gnome- shell/gnome- shell.css This would consistent theming of the lock screen, which doesn't appear to obey the control panel setting. Using the soft-links also makes it easier to spot when those files get overwritten by updates.
So it looks like the changes introduced in 3.30.1- 2ubuntu1. 18.10.1 makes it impossible to follow symlinks from /usr/share/ gnome-shell/ theme/Yaru/ gnome-shell. css ? I guess it's perhaps debatable whether the standard gnome-shell package should reference a hardcoded theme (or maybe that's a GNOME limitation?)
Anyway, since I've worked around this issue, I guess this bug can be closed.