Hi,
After the latest release, the papirus icon for deja-dup is no longer working.

try remove papirus-icon-theme and install again, maybe it's bug package manager with symlinks:
sudo apt purge papirus-icon-theme
sudo apt update
sudo apt install papirus-icon-theme
@alecbcs this is Ubuntu Budgie or Solus?
@varlesh I'm not sure that this is possible.
Hmm. It's strange. org.gnome.DejaDup.svg symlink exist, any broken symlink is missing, but Deja-Dup uses the default icon:

@SmartFinn Либо кривой desktop-файл, опцию поди какую-нить добавили. Либо кеш наверн тупит
After gtk-update-icon-cache:

The .desktop file looks good.
Ну вот, опять этот кеш. Значит автоматическое обновление кеша не работает, прописывай вручную
я про postinst
@varlesh
Ну вот, опять этот кеш. Значит автоматическое обновление кеша не работает, прописывай вручную
Это в Solus. Не торопись с выводами.
Сорри, я думал ты в убунте гноме
That after a re-added executable bit on org.gnome.DejaDup.desktop file:

@JoshStrobl looks like papirus-icon-theme package doesn't build icon-theme.cache at all. Do not you think that this is a bug?
Yea this is something that would need to be sorted as a post-install, but will have to wait until sol (our future replacement for our package manager, eopkg) or when we get around to centralizing all of our actionable scripts. This is something @alecbcs should've raised with us, so I would considered this issue closed, since there won't be action on it for the foreseeable future (let alone downstream), and have Alec raise an issue in our Phabricator instead.
@SmartFinn thank you for all your help. Sorry for posting this bug here I guess it turns out that it is a Solus bug not a Papirus bug after all. I'll take @JoshStrobl's advice and create a bug report on Phabricator.
Most helpful comment
Yea this is something that would need to be sorted as a post-install, but will have to wait until sol (our future replacement for our package manager, eopkg) or when we get around to centralizing all of our actionable scripts. This is something @alecbcs should've raised with us, so I would considered this issue closed, since there won't be action on it for the foreseeable future (let alone downstream), and have Alec raise an issue in our Phabricator instead.