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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
But why bringing discussion about kernel and glibc patches here?
Are there any problems with getting those changes accepted into upstream by corresponding project maintainers?
I find myself wondering if anybody is testing these changes on a AMD APU based Chromebook using Steam installed through ChromeOS's native Debian Package support?
I doubt anyone is testing this particular configuration, since it's quite extraordinary, but you can be the one to test and report issues. That's how Free Software actually work. Must add, I presume, those issues should be driver related, not Proton related.
Also, while common, this is pretty perverted configuration for a GNU/Linux PC.
May I ask what's your reason of using it. Is getting something better not an option for you?