Installing extensions fails when gnome_user != ansible_user

[mjbogusz]

When trying to install extensions for a secondary non-sudoer user I've found 2 problems:

First, restarting the shell doesn't work (#28 (comment)) - this might be due to permissions, due to another user logged in, or maybe no user logged in at all - besides #30 (which would help) I think the restart step should be allowed to fail gracefully.

Second, more important - neither gnome-extensions nor gnome-shell-extension-tool can see the installed extensions (or in fact the whole dconf database) when 'becoming' the target user, probably due to some environment variables set/passed by SSH and ansible.
To replicate, first ssh into a system as a user with some extensions and run gnome-extensions list --installed (this should work as expected); then ssh into the same system as other user, su (or sudo -u) onto the target user and run the command again - the list will be empty.

Ref #28 - I've posted some initial findings there, before it became clear that it's a slightly different issue.

As during debugging I've found a method to setup system-wide extensions for all users (https://help.gnome.org/admin/system-admin-guide/stable/extensions-enable.html.en), which suits my specific usecase much better, I'm switching to that but leaving this report here for other's reference.

[PeterMosmans]

Hi @mjbogusz - thanks for the detailed bugreports, that will definitely help.