New comment by okawo80085 on void-packages repository

https://github.com/void-linux/void-packages/issues/41388#issuecomment-1873340478

Comment:
Well, updating `glibc` to the recently merged 2.38_2 version that has the fix for EAC to not crash brings it back to life, and it does start now, only issue is that it fails with a network error now x)
![image](https://github.com/void-linux/void-packages/assets/43695253/c64abcac-f96f-4654-8113-4ee7c979ea84)
Which is weird, cuz looking at EAC logs it finishes the download, but the callback throws an error?
```
[2024.01.01-13.37.29] Download Progress: 90
[2024.01.01-13.37.29] Download Progress: 100
[2024.01.01-13.37.29] Download Progress: 100
[2024.01.01-13.37.29] Download Progress: 100
[2024.01.01-13.37.29] Download Progress: 100
[2024.01.01-13.37.29] [Connection] Connect result: No error (0) Response Code: 200 Destination IP: 18.244.146.77
[2024.01.01-13.37.29] Download Progress: 100
[2024.01.01-13.37.29] [EAC Callback] Code: 509. Message: 'Unexpected error. (#1)'.
```
Not sure if its related to the new `glibc` update, it did disable cryptography functionality from `glibc` and instead moved it to `libxcrypt` , you can find more in the `glibc` package MR https://github.com/void-linux/void-packages/pull/45501

I wonder if preloading steam with `libxcrypt` will help it :thinking: