Olivier Tilloy

For firefox, the lack of NativeMessaging support in the snap is being tracked by [bugzilla bug #1661935](https://bugzilla.mozilla.org/show_bug.cgi?id=1661935), and there's [a proposal for an XDG desktop portal](https://github.com/flatpak/xdg-desktop-portal/issues/655) to solve the case...

This problem affects node-sha.js (and its reverse dependencies node-createhash and node-crypto-browserify) in Ubuntu, with the upgrade to nodejs 12.18.1: https://launchpad.net/bugs/1887144. Something in nodejs 12.18.1 appears to break the SHA-1 hashing...

I'm not sure whether this is acceptable from a security perspective, as this means that any strictly confined snap can access files temporarily extracted by an unconfined file-roller, even if...

Following up on #32227, I'm interested in working on this. Can someone please assign to me?

This is functionally equivalent, but wouldn't it be more readable to have: append_dir LD_LIBRARY_PATH "$RUNTIME/lib/$ARCH" instead of: append_dir LD_LIBRARY_PATH "$RUNTIME"/lib/"$ARCH"

That's not a requirement from my end, rather a mere suggestion. I'm curious what others think about it.

I wonder if that's really desirable. If a snap build uses custom flags (or even a different compiler) that trigger an obscure compiler bug, the risk is that two snaps...

I tried to reproduce the problem in a VM with what I hoped would be a similar setup, but no luck. However the code in https://github.com/ubuntu/snapcraft-desktop-helpers/blob/master/common/desktop-exports#L209 looks like it might...

@NuclearNemo, @NoraCodes: could you please share the contents of `~/.config/user-dirs.dirs` and `~/snap/chromium/current/.config/user-dirs.dirs` (replace "chromium" by the name of the snap with which you're observing the issue) ?