安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
The game produces no output on the console by default. If I set LD_DEBUG=libs,symbols when I launch Steam, the 250MB log file contains:
4998: /lib/libGL.so.1: error: symbol lookup error: undefined symbol: glActiveStencilFaceEXT (fatal)
4998: /lib/libGL.so.1: error: symbol lookup error: undefined symbol: glBlendEquationSeparateEXT (fatal)
4998: /lib/libGL.so.1: error: symbol lookup error: undefined symbol: glProgramEnvParameters4fvEXT (fatal)
4998: /lib/libGL.so.1: error: symbol lookup error: undefined symbol: glProgramLocalParameters4fvEXT (fatal)
from Puddle (pid 4998 in this run).
This makes me wonder if Puddle is violating the GLX ABI and trying to link directly to driver-exported symbols.
When I launch Puddle then examine its virtual address mappings to get the loaded libraries - including runtime dlopen()ed libs `ldd` can't see - I find:
$ grep -v Steam /proc/5333/maps | grep \.so | awk '{ print $6; }' | sort -u
/usr/lib/dri/i965_dri.so
/usr/lib/ld-2.16.so
/usr/lib/libc-2.16.so
/usr/lib/libdl-2.16.so
/usr/lib/libdricore9.1.0.so.1.0.0
/usr/lib/libdrm_intel.so.1.0.0
/usr/lib/libdrm.so.2.4.0
/usr/lib/libglapi.so.0.0.0
/usr/lib/libGL.so.1.2.0
/usr/lib/libm-2.16.so
/usr/lib/libnsl-2.16.so
/usr/lib/libnss_files-2.16.so
/usr/lib/libpciaccess.so.0.11.1
/usr/lib/libpthread-2.16.so
/usr/lib/libresolv-2.16.so
/usr/lib/librt-2.16.so
/usr/lib/libxcb-dri2.so.0.0.0
I'm an experienced C programmer and I'm comfortable with gdb etc, so I'm very happy to help the team with testing debug-enabled builds if I can do anything that'll help you out.
Going to do some runs with various GLX debug options; I'll follow up with more info.
https://github.com/ValveSoftware/steam-for-linux/issues/1990
As I noted there you can force software rendering to see if you're experiencing this driver-specific issue... though you'll get a pretty slide-show.