org.libreoffice.LibreOffice VS bubblewrap

Flatpaks continue to horrify me because of fundamental stuff like this that keeps getting completely ignored: https://github.com/flathub/org.libreoffice.LibreOffice/issue...

I swear, Desktop Linux has continued to regress in a downwards spiral since Mac OS X was first released, so only for about the past two decades.

Had a quick look at the Flathub repo and it doesn't seem like that's a deliberate decision. In fact only a minute before I started looking for that, someone opened a pull request to enable Qt: https://github.com/flathub/org.libreoffice.LibreOffice/pull/233 As of this moment the build check failed but unless the maintainers are actively opposed to that option, I see no reason to complain.

The latest releases of LibreOffice are 7.5.0 and 7.4.5. So it's possible the issues you're having have been fixed. The easiest way to use software not included in the package repositories is with flatpak and flathub. If you still have problems, you search or report the bug.

Bugs only appearing in the Flatpak version should be reported to Flathub.

Yes, Caolán fixed it.

Nothing nix specific but you may be interested in https://github.com/containers/bubblewrap

Recently, I came across Chainguard and wrote the article How to build Docker Images with Melange and Apko. As a fervent supporter of Kubernetes and GitLab CI, I was eager to experiment with building images using Melange in this particular setup. GitLab's shared Runners work seamlessly with Bubblewrap, eliminating the need for additional configurations. This post is intended for enthusiasts like myself, interested in hosting their own Kubernetes Runners and leveraging the Kubernetes Runner Type of Melange.

```

This is basically manually invoking what Flatpak does:

https://github.com/containers/bubblewrap

This is also useful for more than just security. E.G., you can test how your app would behave on a fresh install by masking your user configuration files. I personally also have a tool that uses it to basically bundle all dependencies from an entire Linux distribution in order to make highly portable AppImages— Been meaning to post that, will get around to it eventually maybe.

The flags above should hide your user data (`--tmpfs`), disable network access (`--unshare-all`), hide/virtualize devices and OS state (`--dev` and `--proc`), and make the rest of the root filesystem read-only (`--ro-bind`­— Including the insecure X11 socket in `/tmp`, which you might want to expose for GUI apps).

Check them against `bwrap --help`; I might have omitted one or two more things you'd need.

While trying to find out more comparison information, found this light on details issue:

https://github.com/containers/bubblewrap/issues/81

It mentions nsjail and minijail.