New comment by SpidFightFR on void-packages repository

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

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://private-user-images.githubusercontent.com/43695253/293589005-c64abcac-f96f-4654-8113-4ee7c979ea84.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDYxMzcwODQsIm5iZiI6MTcwNjEzNjc4NCwicGF0aCI6Ii80MzY5NTI1My8yOTM1ODkwMDUtYzY0YWJjYWMtZjk2Zi00NjU0LTgxMTMtNGVlN2M5NzllYTg0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTI0VDIyNTMwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRmYjI3ODM2NGMyZmQ1ZWVjZTU5MjM3MTg5OGMwNWI1NGU1YjYxODI1NjhmNDUyY2RjZTcyNWQ3MzMyZGM2ZjQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ig3-nqutrTJjnzF68zTyovifcjZ2c-5wpqFPo87ldW8) 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 #45501
> 
> I wonder if preloading steam with `libxcrypt` will help it 🤔

I thought i was going crazy there... So it is a glibc problem specific to void ?