g3nsvrv
g3nsvrv
ok, I tried to upgrade each one manually, and it seems that `glibc-2.42+r3+gbc13db739377-1` broke the whole thing... nice.
rolling back to `glibc-2.41+r48+g5cb575ca9a3d-1-x86_64` resolved the issue temporarily
ok, I have upgraded `wsl` to the latest version once again using `wsl --update` and everything works fine. In short, there is an issue with: - `WSL 1` - `glibc...
yep, indeed. I tried once again on a vm that I have that uses the same version of windows, but everything is clean and by default, and indeed, after upgrading...
> This sounds like [#2595](https://github.com/microsoft/WSL/issues/2595) @Marc-Aldorasi-Imprivata yes and no. it seems that issue mutated a lot, which lead into the glibc issue, but the original issue was something else.
> Experiencing the same issue here with the same "resolution" of using that workaround, but i guess the issue here should be raised within glibc itself in case? i don't...
> Thank you all for reporting this ! > > To give an update, the issue is indeed [#2595](https://github.com/microsoft/WSL/issues/2595). WSL1 currently doesn't implement TCGETS2, which causes packages built on glibc...
> Please post each of the file contents for ; > waydroid.cfg > waydroid.prop > waydroid_base.prop > I did, is attached above
> Yeah, this loads the Netease logo screen and then constantly tries to reload the app over and over again. Same happened to me
@SagaPDev idk if you can change models on waydroid, but the mumu player, where destiny runs just fine on windows, uses: - Samsung Galaxy S24 Snapdragon (SM-S9210) - GPU Adreno...