glibc 2.33 does not work for intel cpu pre-sandybridge

chuck

Hi there,

Today I dusted off my old pc to play some games on linux. Unfortunately the current glibc package contains a bug (https://sourceware.org/bugzilla/show_bug.cgi?id=27318) which prevents my games from loading. It is supposed to be fixed in the next version so I'm wondering when that might hit the repo?

Error message below:
`Starting app 238960

Adding process 6878 for game ID 238960
GameAction [AppID 238960, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
ERROR: ld.so: object '/home/he/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 238960, ActionID 1] : LaunchApp changed task to Completed with ""
Adding process 6879 for game ID 238960
Adding process 6880 for game ID 238960
/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6: CPU ISA level is lower than required
Game removed: AppID 238960 "", ProcID 6878
Uploaded AppInterfaceStats to Steam
Exiting app 238960`

Thanks.

DataDrake

chuck I don't think this is our libc. Pretty sure that's the one being provided by Proton. You might dry a different version of the Proton runtime. Looks like you are running Path of Exile? ProtonDB suggests Proton 6.3-6: https://www.protondb.com/app/238960

If you're still having problems, this might be one of those times where going into Linux Steam Integration and disabling the Native Runtime is necessary (don't forget to restart Steam after).

joebonrichie Our build server is westmere and surprisingly no one has encountered this so far. I'm guessing your system is older than westmere.

Sandybridge is newer than Westmere and it looks like this is using a vendored libc, not ours, afaict.

joebonrichie

It may be better to post this to the dev tracker instead. dev.getsol.us.

Our build server is westmere and surprisingly no one has encountered this so far. I'm guessing your system is older than westmere.

chuck

Thanks for the help! DataDrake you're right it appears to be a Proton issue. I'll play around with different versions / use Linux Steam Integration.