CrewLink perpetual MENU; Please re-open CrewLink as Administrator

[deckk]

I receive no errors from Crewlink (installed from AUR crewlink-bin) when opening once in the game. Even if I'm in a lobby the window just says "MENU" in a box at the top. If I run from the terminal I get the following error repeatedly once in a lobby:

error: process_vm_readv returned -1 instead of 4 (Operation not permitted) address=0x4b47f54

Seeing as it was returning Operation not permitted I figured I should try running with sudo.

$ sudo /opt/CrewLink/crewlink --no-sandbox
$ sudo -E /opt/CrewLink/crewlink --no-sandbox

Using either of these lines result in this error in the CrewLink window:

ERROR Couldn't connect to Among Us. Please re-open CrewLink as Administrator. Need help? Get support

---

Let me know if this should be separated into two issues.

[deckk]

Seems to be the same issue #1

I'm on Manjaro, kernel 5.10.4-2-MANJARO, so I presume if I were on stock Arch with stock kernel it would be working.

[Denton-L]

If you're using the AUR package, make sure you're using crewlink-launcher instead of running crewlink straight-up. It sets kernel.yama.ptrace_scope=0 so that CrewLink can listen in to Among Us. Alternatively, before running CrewLink, run echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope.

[deckk]

Thanks @Denton-L, that seemed to help as I now see the lobby code and myself and others in the CrewLink window, and my icon now lights up when I speak - however, I still can't actually hear anyone and no one can hear me. The friend I tested it with was running 2.0.1 from the original Ottomated repo, but unfortunately this Linux fork is still a couple releases behind at 1.2.1.

I was originally running from terminal because hitting Super and running CrewLink from there doesn't work (Cinnamon start menu). Could you clarify if I need to run sudo tee... when running crewlink-launcher from terminal or not?

I hope that once this repo's updated it will work... And thanks again for your comment!

[Denton-L]

The friend I tested it with was running 2.0.1 from the original Ottomated repo, but unfortunately this Linux fork is still a couple releases behind at 1.2.1.

I was able to use v1.2.1 with my friends who were using v2.0.1 (albeit, I was missing the new features like being able to hear ghosts). When in doubt, try doing a Ctrl+R and hopefully that'll magically fix things.

Could you clarify if I need to run sudo tee... when running crewlink-launcher from terminal or not?

Nope, crewlink-launcher should take care of that process automatically for you.

[deckk]

Thanks for the help. Unfortunately it still doesn't work. Joined a lobby and everyone could hear each other except me, and I could hear no one. Apparently I had the red WiFi icon but after changing my mic and exiting the settings it went away - but the problem persisted regardless.

Thanks again for responding to me before. Not sure what else I can try...

[ItsRogueRen]

I have this as well on Pop!_OS 20.10 (Ubuntu based, no AUR) I downloaded and ran it with the terminal commands on the releases page

EDIT: Hitting ctrl+r after going into a lobby fixed the admin issue, but now I have the Bad address issue mentioned in another report error: process_vm_readv returned -1 instead of 4 (Bad address) address=0xfffffffffebd7f54