So far the only weirdness on fedora is just kinda adorably weird: every flatpak app seems to crash on first launch. After that, they're fine.

Sadly, being weird proprietary things they don't plug into the crash reporting infrastructure, so who knows what their malfunction is. I don't get any option to report a crash 🤷 coredumpctl has crash dumps for both, discord did a SIGABRT and slack a SIGTRAP (lol)

oh and as soon as I post that, I find an answer from several years ago that it's probably slack and discord both using an ancient version of _something_, which runs afoul of a syscall sandbox and gets them nuked from orbit. Love to run software that doesn't keep its dependencies in check 🙃 At least I have some verification that the various layers of sandboxing are doing stuff.
@danderson huh. I thought flatpak was a single file kinda thing but it's not that at all.

@zrail nope it ships full filesystems (with layering stuff for dedup), which run inside a sandbox that's been tailored for desktop applications - so they get limited access to APIs for stuff like "please pop a file selector and let me see one file from outside the sandbox", or "please may I have a webcam and mic to do some videoconferencing".

It has the traditional problems of shipping separate copies of libraries, but no worse than the docker universe everyone's embraced. It's neat.

@zrail @danderson I quite like it apart from having to make aliases or whatever so I don't have to `flatpak run tld.path.damn.Entire` to get an application running.