Rusty Corgi<p>I fell down an interesting rabbit hole with Telegram. Telegram-Desktop uses Jemalloc which seems to run into some problems with the 16k page sizes on Asahi Linux. If you build from the RPM package it builds fine because the version of Jemalloc for Asahi is built using 16k page sizes. That said, if you use the Flatpak version, it's built for 4k page sizes and crashes out. </p><p>Since Jemalloc can only have the page sizes set at build time and not runtime, how exactly would you fix the Flatpak version without breaking out of the Flatpak sandbox and linking the system install of Jemalloc? :wolf_peek: And how does Flatpak usually handle other similar edge cases where different build options are needed even on the same architecture?</p><p><a href="https://cubhub.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://cubhub.social/tags/AsahiLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AsahiLinux</span></a> <a href="https://cubhub.social/tags/Flatpak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Flatpak</span></a> <a href="https://cubhub.social/tags/Telegram" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Telegram</span></a> <a href="https://cubhub.social/tags/TelegramDesktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TelegramDesktop</span></a></p>