@Atemu This broke zulip. Any advice on debugging?

Not too familiar with Electron, sorry.

I noticed that AppImage was using Chrootenv and found out that all our packaged AppImage apps work with the new bubblewrap FHSEnv -or so I thought.

I must've missed Zulip somehow. It's the last one alphabetically which might explain it but my bash_history tells me that I did in-fact execute it when drafting this PR.
I tried Zulip from this PR's HEAD and even had it run in a VM of my config to rule out other environmental factors but it must have already been broken back then.

The immediate fix would be to return zulip's appImageTools' FHSEnv builder to Chrootenv. That's fine as we're in the process of transitioning anyways but we should obviously also find out why it doesn't work under Bubblewrap in NixOS (The Flatpak uses the same tech and works fine, that's not it).

I found the -d flag for appimage-run and appRun reads the DEBUG env variable to print its env. They're ENVs are identical though and the debug output isn't very insightful.

What I've also found out is that the app still seems to function: You can open the dev console with C-I and use the "File" "Edit" etc. buttons in the top (e.g. click top left corner and then press q); it just doesn't display anything.
Speaking of which, is your blank screen darkish-grey too or is it white?

The biggest difference between Chrootenv and bubblewrap is how the actual FHSEnv is constructed; the directory structures (especially /etc) are very different.
I have a hunch the issue lies here.

@Atemu For now then #99930