Some emulation and virtualization tools have dependencies on page size. We had some page size issues in Firefox initially, though I think we smoked most of those out.
Maybe that is why Thunderbird is not working at all either.
Simply running a 4k kernel doesn't always fix the issues. Sometimes it is necessary to rebuild each broken application on the host running a 4k kernel. This is because the build scripts of some applications look at the page size during compile time and assume it will be the same for run-time and they hardcode it into the binary.
I will probably try building both the Firefox and Thunderbird packages from source on a Debian buster host running with the 4k page size.
I tried Firefox for a WebRTC call yesterday and the video was missing, I'll see if that works with the 4k page size too, with and without recompiling Firefox itself.
The two biggest concerns I heard from people about this platform are not being able to use Firefox reliably and the noise issues. Developers are reluctant to embrace any platform that might sidetrack us from the things we are supposed to be working on. If the noise issues can be
fixed with Vikings' water cooling solution and the Firefox issues can be reined in by a 4k page size then it could make a crucial difference to the success of the platform. It is therefore quite important to look at how to engage distributions in that solution.