Copying my post from the original Linux Ban thread.
+1 banned Linux/Proton user here, and sadly got the banhammer suddenly about about 5 hours ago now out-of-the-blue. NEVER CHEATED, played the game for 435 hours already (according to Steam), and was just playing a couple of Trios & LTM games w/ my friend when suddenly I got the "this client has been banned: banned" Error when we were entering the Firing Range. This error persists whenever I try to enter a game, but weirdly I'm still able to access my Lobby (even though from what I understand banned accounts are not even supposed to be able to enter Lobby?)
PC specs are as follows (mostly same specs as @ungergames PC):
- Kernel: 6.4.6-76060406-generic
- DE: GNOME 42.5
- Theme: Pop-dark [GTK2/3]
- Icons: Pop [GTK2/3]
- Terminal: gnome-terminal
- CPU: AMD Ryzen 7 3700X
- GPU: NVIDIA GeForce RTX 2070 SUPER
- RAM: 32GB
I'm currently logged in to my Win 10 dual-boot to double-check the ban, so I'll update the specs w/ Launch options I used. IIRC it's supposed to be the default one set by Steam initially.
I was thinking that the 'ban' maybe due some Linux-EAC hiccup that may have occurred due to recent update, but sadly switching to Win10, ban is still active on Win 10, so it's not just a bug.
I tried running the game through EA App in Windows 10, and it seems the EA Account is already linked to the Steam account, so my ban already effected the EA account as well. Just written a support request, and will be updating if there are any updates.
If my hunch is correct and indeed this issue is triggered again due to recent patch, I'm expecting similar reports to be flooding in within the next few days. In which case, hope this 'false positive' ban gets resolved soon.
One 'funny' thing I'd like to note is that the ban doesn't seem to get synced w/ my EA account, as it doesn't show up when I check for 'Ban History', as seen in screenshot. Either this is further proof that the ban I got was 'false positive', or EA's system broken again causing the de-sync.