F44 broke some appimages

[plush mauve]

Some AppImages haven't been working since the update to f44. I layered FUSE just like I did before the update. But since the update whenever I try to launch an AppImage I always get the message
"fatal allocator error: invalid uninitialized allocator usage
Aborted (core dumped) ./signal_beta.appimage"

In addition to the Signal AppImage which is currently in beta I also tried Joplin, and the same error occurs there. While some others such as Ryubing or 0 A.D. the error does not occur, and they work just as they did before.

[clever zinc]

there are some changes that have occurred relating to how preloads are handled. Did you try with ujust with-standard-malloc

[plush mauve]

Thanks that worked. I just didn't think of it because it had been working fine before.

[clever zinc]

It's not yet clear what changed in F44 to cause this. @sleek ocean It seems this is consistently reproducible, but at the same time it seems like a good thing. As in, hardened_malloc is being more consistently preloaded

[sleek ocean]

Hub, strange

[clever zinc]

i guess the question might be why it wasn't being preloaded before for appimages? maybe a bug was fixed? 🤔

[sleek ocean]

yeah no idea. I do think it's still worth considering switching back to the bwrap method of opting out of hardened_malloc, with SELinux policy so it doesn't require enabling unconfined-domain userns. the method we use with LD_PRELOAD feels a bit patchwork and prone to being unintentionally disabled by anything that clears env vars

and the trick with making /etc/ld.so.preload readable only by root feels like a hack lol

[clever zinc]

that or do it the proper way ™ https://github.com/secureblue/secureblue/issues/293

but that would mean figuring out a new way to handle overrides

[sleek ocean]

yeah I think that would require bundling glibc malloc as its own shared library that could be preloaded

which is probably doable but feels like it might be more error-prone than the ld.so.preload method