That blogpost is considered to be somewhat flawed with its information, as explained here: https://tesk.page/2021/02/11/response-to-flatkill-org/
#NoBot #NoIndex #NoBridge
That blogpost is considered to be somewhat flawed with its information, as explained here: https://tesk.page/2021/02/11/response-to-flatkill-org/
You can, infact there’s outright a mesa git runtime one can add, i don’t imagine too many systems roll so fast as to outpace it https://docs.flatpak.org/en/latest/available-runtimes.html
Two utilities that may be handy for you here:
Pakrat: Automates and simplifies the process of creating alliases for flatpaks, good if you just need to make a few programs be simplified
Fuzzpak: Lets you do fuzzy searches for flatpaks(as in you just write fuzzpak inkscape and it auto looks for something with inkscape in the flatpak folder and launches it), good for when you want to simplify launching flatpaks in general without doing the process of configuring stuff manually
Are you using Firefox within a flatpak perchance ?
There seems to be a bug to it relating to use of bitmap fonts, you can fix the issue by disabling them via a config file in firefox’s fonts: https://bugzilla.mozilla.org/show_bug.cgi?id=1621915
No, that’s a different protocol, the tearing patches, already merged, but i believe we’re still waiting on some patches to the kernel to get them fully working(i think it was kernel 6.8 that had them), Nvidia’s drivers also need to add support for it, they’ve given no timeline for that so far however
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/65