Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
... you can see quite a few, presumably running in a loop. When the game terminated I looked at the last one, which in my case the was /proc/2554/cmdline. Examining that:
Unfortunately I lost the terminal output, but in this case it was Chrome's GPU process. Quitting out of Chrome allowed the game to start without any trouble.
For whatever reason it seems the game mis-identified the wrong process as an already-running instance of the game and terminated. I think in this case it might be related to Chrome's occasional use of /proc/self/exe to spawn child processes, but I wasn't able to get the bug again when I restarted Chrome (its GPU process hadn't been launched via /proc/self/exe for some reason).
If any of the devs see this hopefully it'll help solve the issue, although I think it may be a bug with Unity. The "Player is already running" bug seems to be fairly common for Unity games under Linux, and in the few instances where others have (inadvertently) solved it, its always been by closing Chrome or logging out and back in.
When this happens, what's in the conflicting cmdline file? Was it actually "/proc/self/exe" ?
Killing this process resolves the problem and the game will launch. Unfortunately I could not reproduce the problem; restarting Mattermost led to the instance in question here being launched as a normal electron process, not using /proc/self/exe
/proc/self/exe--type=renderer--field-trial-handle=5509477849240657217,6797439337003870637,131072--disable-features=SpareRendererForSitePerProcess--lang=en-US--app-path=/usr/lib/mattermost-desktop/app.asar--no-sandbox--no-zygote--preload=/usr/lib/mattermost-desktop/app.asar/browser/webview/mattermost_bundle.js--context-isolation--background-color=#fff--guest-instance-id=4--enable-blink-features--disable-blink-features--hidden-page--enable-websql--num-raster-threads=4--enable-main-frame-before-activation--service-request-channel-token=12639844217821139103--renderer-client-id=11--no-v8-untrusted-code-mitigations--shared-files=v8_context_snapshot_data:100,v8_natives_data:101
I think the problem here is that WL2 is resolving `/proc/self/exe` in its own context and finding its own binary.