Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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?