`xdg-open` moved in `core` and stopped working

This is happening with all the snaps I have installed. This has been going on since the latest update.

sergiusens@mirkwood:~$ snap run --shell telegram-sergiusens.telegram
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

sergiusens@mirkwood:/home/sergiusens$ which xdg-open 
/usr/bin/xdg-open
sergiusens@mirkwood:/home/sergiusens$ xdg-open https://google.com
bash: /usr/bin/xdg-open: Permission denied
sergiusens@mirkwood:/home/sergiusens$ exit

And another snap:

sergiusens@mirkwood:~$ snap run --shell corebird
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

sergiusens@mirkwood:/home/sergiusens$ xdg-open https://google.com
bash: /usr/bin/xdg-open: Permission denied
sergiusens@mirkwood:/home/sergiusens$ cat /usr/bin/xdg-open
cat: /usr/bin/xdg-open: Permission denied

In the generated apparmor profile for corebird I can see this:

# Snappy's 'xdg-open' talks to the snapd-xdg-open service which currently works
# only in environments supporting dbus-send (eg, X11). In the future once
# snappy's xdg-open supports all snaps images, this access may move to another
# interface.
/usr/local/bin/xdg-open ixr,

Which is the old path.

Last updated 1 year, 4 months ago. Help improve this document in the forum.