Cài đặt Steam
đăng nhập
|
ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuậ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?