knarrff
Assigned
Reported
Comments
At least for me, there does not seem to be any new version. The launcher is not updating and I still get the same file contents:
$ md5sum .minecraft/launcher/liblauncher.so
b6278a946bb98d2039e43a6de36cd24c .minecraft/launcher
Given that the duplicates are not even marked as such, the devs likely simply didn't have the time to look at it properly and apparently this also isn't a priority for them. So, for now, for us, it is "wait and vote".
Since I cannot vote atm, one "me too"-comment, with the small addition:
before the update:
$ md5sum .minecraft_2022-08-23/launcher/liblauncher.so
ef6c86ec1e39c1b81563d6d0163252ba .minecraft_2022-08-23/launcher/liblauncher.so
$ strings .minecraft_2022-08-23/launcher/liblauncher.so | grep GLIBC_2.2
GLIBC_2.2.5
after the update:
$ md5sum .minecraft/launcher/liblauncher.so
b6278a946bb98d2039e43a6de36cd24c .minecraft/launcher/liblauncher.so
$ strings .minecraft/launcher/liblauncher.so | grep GLIBC_2.2
GLIBC_2.2.5
GLIBC_2.29
GLIBC_2.25
GLIBC_2.28
The new dependencies come through usage of (in case that helps you find it):
$ nm -D .minecraft/launcher/liblauncher.so | grep GLIBC_2.2 | grep -v 2.2.5
U fcntl64@GLIBC_2.28
w getentropy@GLIBC_2.25
U pow@GLIBC_2.29
Also: deleting .minecraft did not help either. The first time it starts in that case, with the files presumably from the debian-package installer, the second time (after the update) you get the same problem.
@Joe Smoe: I think we get what your message is. However, if you want to be taken seriously, you'll have to work (hard) on how you deliver it. And I really had to try hard to make this sound nice.
@devs: thanks. It still introduces a dependency on 2.25, which was not there previously, but it is a weak one. Not sure why that was intentional or not.
```
$ nm -D .minecraft/launcher/liblauncher.so | grep GLIBC_2.2 | grep -v 2.2.5
w getentropy@GLIBC_2.25
```