Nindaleth

Current measurement of the same scene on latest cc35d6df (still the same hardware, still 1440p and 100% render resolution, all extended graphics features enabled): 80/35 FPS. For comparison, I get...

I wish I was making this up, today I tested an RT optimization that [landed](https://www.phoronix.com/news/RADV-RT-Much-Faster-Mesa-24.0) a few days ago in Mesa. :smile: From September's 70/30 to November's 80/35 to January's...

Hi, I also get a crash immediately on launch without seeing any UI. Version 1.0.0 from F-Droid, Android 13 (Motorola so almost stock Android). Here's a backtrace that I get,...

For the record, I've downloaded the 1.0.2 APK from the Releases and it crashes at the same time with the same backtrace.

@cjpais Here's a short video, it shows how toggling the maximization (both on and off) unlocks the title bar buttons. Since the screencasting software doesn't show that in any way,...

I can reproduce the issue on a Thinkpad T490 (Core i7-8565U) laptop and a self-built desktop (Ryzen 1700X). But I don't type _that_ fast, promise! When I try it on...

> could it be an glibc issue? Not sure, mine is just a smidge older (at least until I upgrade to Fedora 39, haha). Should still be newer than the...

For the record, when actively reproducing the issue, I get it with around 10-20% probability. The glibc is essential and its authors put great efforts in keeping it backwards compatible....

Yes indeed, Fedora runs on Pipewire, but then I'd expect my builds to get KILLed and the Ubuntu CI artifacts to work fine. I suspect something is happening in kernel...

I've just tested on a Fedora live USB and there are no issues either. In other words, the builds actually seem to run everywhere just fine and don't need to...