Thank you for the report, especially the link. That is worth reading.
Although it points to a glibc patch, and tells the enquirer how to apply it, it starts:
"My honest suggestion is to leave GLIBC alone ... As you already suspect, the huge risk is to break your entire system, arriving to be impossible to execute any program."
and ends:
" If you install Flatpak from slackbuilds, and follow the setup for steam: https://flathub.org/apps/details/com...software.Steam
This allows EAC games to load correctly within the sandboxed environment, as i assume it's using its own glibc version in the sandbox which is less than 2.36.
Might be a better temporary alternative for affected games by using Flatpak, until glibc or EAC/EOS gets an upstream fix."

Yes, I did note that you are aware of this:
> It does work on the latest flatpak steam but I prefer mga packages..
A nice remark, but it is likely that you will have to Flatpak this at present.

For 'glibc', assigning to basesystem.

Assignee: bugsquad => basesystem
Source RPM: (none) => glibc-2.36-28.mga9.src.rpm

We as Mageia shouldn't revert or patch away the root cause of this: Epic as developer of this rootkit called EAC (Anti Cheat enginges are rootkits) aren't capable of clean coding. DT_HASH is deprecated since 10 years and Epic still uses this deprecated function in their rootkit. The developers of glibc now wan't to do the final transition away from the deprecated DT_HASH towards DT_GNU_HASH.
There is alot of FUD that glibc breaks ABI and stuff like that. No! Epic is incompetent to properly code their rootkit!

As long as the glibc developers don't decide to revert their decission, we shouldn't apply this "patch" to enable the EAC rootkit again..

Here some more technical background:
https://maskray.me/blog/2022-08-21-glibc-and-dt-gnu-hash

(In reply to Lewis Smith from comment #1)
> Thank you for the report, especially the link. That is worth reading.
> Although it points to a glibc patch, and tells the enquirer how to apply it,
> it starts:
> "My honest suggestion is to leave GLIBC alone ... As you already suspect,
> the huge risk is to break your entire system, arriving to be impossible to
> execute any program."
> and ends:
> " If you install Flatpak from slackbuilds, and follow the setup for steam:
> https://flathub.org/apps/details/com...software.Steam
> This allows EAC games to load correctly within the sandboxed environment, as
> i assume it's using its own glibc version in the sandbox which is less than
> 2.36.
> Might be a better temporary alternative for affected games by using Flatpak,
> until glibc or EAC/EOS gets an upstream fix."
> 
> Yes, I did note that you are aware of this:
> > It does work on the latest flatpak steam but I prefer mga packages..
> A nice remark, but it is likely that you will have to Flatpak this at
> present.
> 
> For 'glibc', assigning to basesystem.

I stop using the flatpak version since I found some problems when trying to change the location of the stored games... I planed to use the same location as the current mageia steam release but it was locked.. I will download the new one and see.

(In reply to sturmvogel from comment #2)
> We as Mageia shouldn't revert or patch away the root cause of this: Epic as
> developer of this rootkit called EAC (Anti Cheat enginges are rootkits)
> aren't capable of clean coding. DT_HASH is deprecated since 10 years and
> Epic still uses this deprecated function in their rootkit. The developers of
> glibc now wan't to do the final transition away from the deprecated DT_HASH
> towards DT_GNU_HASH.
> There is alot of FUD that glibc breaks ABI and stuff like that. No! Epic is
> incompetent to properly code their rootkit!
> 
> As long as the glibc developers don't decide to revert their decission, we
> shouldn't apply this "patch" to enable the EAC rootkit again..
> 
> Here some more technical background:
> https://maskray.me/blog/2022-08-21-glibc-and-dt-gnu-hash

Wow.. Thanks for the info sturmvogel, I wil check it out.

It seems then that it would be better to someone release a patch for EAC.. LOL

I hope Epic fixes this but I think Valve would have to negociate with them for a fix..

Since Epic Games took over the games distribution of Rocket League the Mac and Linux version where canceled... I hope Rocket Leaguep´s dev (Psyonix) would reconsider... Shadow of tombraider is also available for linux on steam except on Epic.

Thanks for everything guys!!

Hello again

Today I installed Steam on Flatpak

The problem is sandboxing.. and I cannot access my downloaded games.

My games are in /mnt/gamedata

flatpak is stored on /var/lib/flatpak/app/ wich is ony 120gb and I can´t seem to find a way to access /mnt/gamedata

No wonder I was not able to import my bookmarks with flatpak´s firefox.

Regards

You need to issue following command as described on the steam flathub site to get access to another drive:
flatpak override --user --filesystem=/path/to/Steam/Library com.valvesoftware.Steam

I reinstalled mageia 9 and used / and swap on the 128gb ssd and /home on the 1tb hd.. it now works great, kind of slow compared to mga 9 steam release but I hope Epic resolves the EAC problem soon.

Regards

Easy Anti Cheat now works.. I guess Epic Games finally fixed it.. at least it works with proton next 7.0-6 and glibc 2.36.30. I tested Proton 7.0-5 and it doesn´t work, I get Failed to load anti-cheat module error.

Proton Experimental did not work... (The one available today)

While testing proton experimental and 7.0-5 something was moved that EAC stop working again even witn 7.0-6...  I will reinstall the game that failed (Multiverus) while in the other hand fall guys works fine.


Cheking on the Easy Anti Cheat module it seems to be the same release from october 2022.

(In reply to Ezequiel Partida from comment #8)

> While testing proton experimental and 7.0-5 something was moved that EAC
> stop working again even witn 7.0-6...  I will reinstall the game that failed
> (Multiverus) while in the other hand fall guys works fine.

Sometimes Steam can be a little bit picky when trying different Proton versions after each other. I found that it is sometimes necessary to close Steam completely before testing a game with another Proton version.

I think this should be fixed upstream Epic / Valve

I will mark this as wontfix

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX