There were lots of other peope having this issue, including myself, who have never installed Mullvad. I think it's related to something in the Ubuntu repos. What fixed it for me was to run:
sudo dpkg --configure -a
sudo apt update && sudo apt upgrade
Some people were also reporting a broken install due to missing packagekit, so maybe ensure packagekit is installed with:
sudo apt install packagekit
Then reboot, and you should be able to update stuff normally now.
uBlock has an "EasyList/uBO - Cookie Notices" filter that you can enable on both desktop and mobile, which is probably enough for most people.
His linktr.ee from his official website links to that account. So it's official.
I think the question is: is it actually him using the account, or is it a social media manager?
I had a similar issue, and it was because my joystick deadzone in SteamOS's settings was too low. The joystick registering an input changed the functionality of those two buttons, registering as a different hotkey/shortcut. It's possible one of your other buttons is stuck, but it might be difficult to figure out which one.
If you accidentally ban linux users in three[1] different[2] banwaves[3], then linux was only halfway supported in the first place, even if they overturned (almost) all of those bans.
I think the real reason they did it was EA's financial situation. Since money is tight, the amount of resources they were willing to put into real linux anti-cheat probably dropped to "none at all," and now we're here. Otherwise other cheater-prone games like Counter Strike, Overwatch, Halo, The Finals, DayZ, Hunt Showdown, etc would have probably dropped/blocked linux by now too.
Doesn't the "EasyList/uBO – Cookie Notices" filter in uBlock's settings do the same thing as IDCAC / consent-o-matic?
If I played any Rockstar games, I'd be unhappy with their new anti-cheat too, since it needlessly blocks linux, but this isn't the way this should be protested. If anything, this probably validates their decision.
The way this should be protested is to just stop playing. Stop giving them money. Stop boosting their month active user numbers that they can flaunt to investors. Hit them financially, since it's the only hit they really care about. There's a sea of other high-quality games you can play instead.
@[email protected] @[email protected], a Respawn employee responded on reddit and wants a list of user IDs/gamertags for those banned on linux:
https://www.reddit.com/r/apexlegends/comments/1fi77vs/comment/lnh13kj/?context=8
EDIT: A Respawn employee on reddit is now asking for the user ID/gamertag of those banned on linux: https://www.reddit.com/r/apexlegends/comments/1fi77vs/comment/lnh13kj/?context=8
Original comment
Looks like you're not the only one:
https://www.reddit.com/r/linux_gaming/comments/1f5kyd1/psa_using_proton_experimental_or_at_least/
https://www.reddit.com/r/linux_gaming/comments/1ffxfjb/apex_legends_proton_epic_bug_that_do_that/
They've falsely banned linux players before, once in March 2023 and again in August 2023.
I got hit in the Aug 2023 ban, and had my permaban overturned after 1-2 weeks. Expect to have your appeal rejected, we had to make enough of a fuss about it to get a community manager to reach out to the development team to get people unbanned:
https://www.reddit.com/r/apexlegends/comments/15uqt7w/linux_users_getting_falsely_banned_again/
https://answers.ea.com/t5/Technical-Issues/Linux-players-getting-banned/td-p/12338557/page/50
I haven't played in 9-10 months since the false positive put a really bad taste in my mouth, so I don't have any datapoints to add for the current state of things, but I wish you the best of luck getting unbanned.
Don't worry, Seth Evans (touring and studio musician for Black Midi) helped produce this song, and Black Midi's drummer (Morgan Simpson) is credited on Greep's new album, which is set to release in a month: https://open.spotify.com/prerelease/6uPLM4h3oBnZ3IKUL4f20H
Cameron Picton is also doing a solo project called CameraPicture or something
I'm not even sure to be honest, was just following the solution that others had posted.
Pop's site says that the
--configure -acommand configures any unpacked but not yet configured packages. And someone on Pop's github theorized it was related to Microsoft adding their own apt source for VSCode. So it was probably some issue with Microsoft's new apt source being unpacked but unconfigured, and that caused something in apt/dpkg to freak out. That's my best guess at least.