TIL that the directories that `snapd` binds are just hard-coded, right in the guts of the thing
TIL that the directories that `snapd` binds are just hard-coded, right in the guts of the thing
@SnoopJ
weird, it *should* work, I think it goes through some kind of portal that has more access rights than the process itself.
I have a Chromium snap installed and in GMail I can't drag'n'drop a file from /tmp/ to attach it, but the "attach files" button which opens a file picker *does* work
@SnoopJ of course it could be that Slack uses the filepicker of its UI toolkit instead of the portal - but I thought it used Electron which should use the same shit as Chromium?
I know of this portal stuff (xdg-desktop-portal) from https://github.com/btzy/nativefiledialog-extended which can use either Gtk3 or the D-Bus based portal on Linux - another advantage of the portal is that it uses a "native" filepicker depending on your desktop, e.g. KDE/Qt one when using KDE. But maybe it's less flexible

Cross platform (Windows, Mac, Linux) native file dialog library with C and C++ bindings, based on mlabbe/nativefiledialog. - btzy/nativefiledialog-extended
@SnoopJ
I literally moved my home directory because using Ubuntu is advantageous for my job (vs any other distro), and snaps/apparmor cannot handle the possibility that a home directory is anywhere other than `/home/`
I'm not un-generous feeling towards the Canonical people. Packaging and distribution are hard. But this is relatively important stuff if you want the project to be taken seriously.
To me, snaps are about as important as upstart (read: I look forward to it being dead).