tinywrkb

Bubblewrap is probably still setting a mount namespace and I don't believe there's a way around this. > I think the easiest way would be to use --with-priv-mode=none with bubblewrap...

p.s. A good example of how to build a Flatpak manually is [the Firefox packaging](https://hg.mozilla.org/releases/mozilla-release/file/tip/taskcluster/docker/firefox-flatpak/runme.sh). edit: This example is missing the compilation step where I suggested building in a chroot,...

If anyone still hitting this then try instead to use the Flatpak package here: #58

@sotch-pr35mac thanks for the update. I will look at this in a couple of weeks.

Bundles have limitations, like the missing extensions support, and I don't think these are of any use for Flathub publishing. It seems like Flathub will allow direct uploads, which will...

> I'm not sure about Flathub allowing direct uploads [Flathub in 2023](https://discourse.flathub.org/t/flathub-in-2023/3808)

I also looked at this problem today, and I think I might go with something like this ``` [Service] Type=forking PIDFile=sway/pid ExecStartPre=systemctl --user unset-environment DISPLAY WAYLAND_DISPLAY ExecStart=/bin/sh -c '/usr/bin/sway &'...

[Here's my own Flatpak manifest for Joplin](https://github.com/tinywrkb/flatpaks/blob/master/org.joplinapp.joplin/org.joplinapp.joplin.yaml), making use of the AppImage release. As Joplin is open source I'm not sure if this would be approved for publishing via Flathub...

@barthalion Thanks for the feedback. I'm not using Joplin at all, so it would be preferred if someone else that knows the app and can notice when something is broken...

In the process of writing my own services, I got to the same conclusions as @alextsits wrote in 1. & 5. Also, I don't see the point of having `wayland-session*`...