I have installed Civilization VI via Steam, but Steam was installed via Flatpak. After updating Freedesktop runtime, blue glitches appears in Civilization VI: Rise and Fall. Previously, I had the same bug, but on older mesa and on OpenSuSE Tumbleweed.
hello. Could you please provide your mesa version and OS? Also, it would be really great to get an apitrace for the issue https://github.com/apitrace/apitrace
>flatpak info -m com.valvesoftware.Steam [Application] name=com.valvesoftware.Steam runtime=org.freedesktop.Platform/x86_64/1.6 sdk=org.freedesktop.Sdk/x86_64/1.6 tags=proprietary; command=steam-wrapper [Context] shared=network;ipc; sockets=x11;pulseaudio;system-bus; devices=all; features=devel;multiarch; filesystems=xdg-music:ro; persistent=.; [Session Bus Policy] org.kde.StatusNotifierWatcher=talk org.freedesktop.NetworkManager=talk org.gnome.SettingsDaemon=talk [Extension org.freedesktop.Platform.Compat32] directory=lib/32bit version=1.6 [Extension org.freedesktop.Platform.GL32] directory=lib/32bit/lib/GL version=1.4 versions=1.6;1.4 subdirectories=true no-autodownload=true autodelete=false add-ld-path=lib merge-dirs=vulkan/icd.d;glvnd/egl_vendor.d download-if=active-gl-driver enable-if=active-gl-driver [Extension com.valvesoftware.Steam.Debug] directory=lib/debug autodelete=true no-autodownload=true [Build] built-extensions=com.valvesoftware.Steam.Debug;com.valvesoftware.Steam.Sources; On this page (https://github.com/flathub/com.valvesoftware.Steam/issues/103) is wrote freedesktop runtime uses 18.0.4 version of Mesa. I don't know if it uses any special flag in build time.
My operating system is OpenSuSE Tumbleweed. I will try to compile apitrace as flatpak app (using freedesktop runtime) and copy it into freedesktop runtime.
I create api dump/trace file, but it is 4 GiB big and I have had internet connection trouble, when uploading. I will try to send it another time.
It would be great. You can download it to google drive, for example, and provide a link here
http://slawek.lach.art.pl/Civ6.trace.tar.gz
Does the blue rendering look like what was reported in 100790?
(In reply to Mark Janes from comment #7) > Does the blue rendering look like what was reported in 100790? Yes.
thanks. Did you try to open and replay this file after creation? Asking because for me it says this: >>>error: unsupported trace format version 6 I checked apitrace version from ubuntu repos, and built manually from source. Possibly that it has difference between my versions - and your's (compiled using flatpak). That's my next step - to build apitrace using it. But before this... just to be sure that apitrace is correct, could you please type "apitrace replay Civ6.trace" ? upd - I also recollected in mind that issue, and first of all - rechecked that apitrace on mesa 18.0.4 For me (SKL) it was ok.
how big is the trace supposed to be? My download was only ~200MB. I got unexpected end of file errors from apitrace and gunzip.
(In reply to Denis from comment #9) > thanks. Did you try to open and replay this file after creation? Asking > because for me it says this: > > >>>error: unsupported trace format version 6 > > I checked apitrace version from ubuntu repos, and built manually from source. > Possibly that it has difference between my versions - and your's (compiled > using flatpak). That's my next step - to build apitrace using it. > > But before this... just to be sure that apitrace is correct, could you > please type "apitrace replay Civ6.trace" ? > > upd - I also recollected in mind that issue, and first of all - rechecked > that apitrace on mesa 18.0.4 > For me (SKL) it was ok. Trace was correctly replayed on my machine.(In reply to Mark Janes from comment #10) > how big is the trace supposed to be? My download was only ~200MB. I got > unexpected end of file errors from apitrace and gunzip. Tarbal has 1,3 GiB of size and trace 1,7 GiB.
(In reply to Mark Janes from comment #10) > how big is the trace supposed to be? My download was only ~200MB. I got > unexpected end of file errors from apitrace and gunzip. I must tell server hosting my side isn't mine and ever I hadn't access to appache configuration. Maybe it break connection, when too big transfer is achieved? I will check.
Seems tar is OK. I'm able to replay, but issue is absent on my configuration OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.5 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 18.0.5 OpenGL shading language version string: 1.30
hi Slawomir. I installed flatpak and built on it apitrace. Then I launched it >flatpak run org.apitrace.Apitrace and selected .trace, provided by you. Trace was played successfully without glitches. Also (and that's most weird for me part) I played old apitrace from here - https://bugs.freedesktop.org/show_bug.cgi?id=100790 And I didn't see an issue too. So it means, that flatpak really uses not system mesa version, but I haven't any ideas, how to check, what exactly was used. To summarize: 1. if I am using apitrace from system, it uses "system" mesa (which I exported before and set 17.2.0, to be sure, that I will see an issue). 2. if I am using apitrace from flatpak, I don't see glitches on both .trace files. And strange thing, I still can't play provided by you .trace, using NOT flatpak apitraces (built or downloaded from repo), so I can't launch the trace on 18.0.4 mesa.
one more thing, could you please also re-play .trace from that old issue, and say whether you see an issue or not. If you see it... I may suppose, that somehow in your environment mesa was downgraded
(In reply to Denis from comment #15) > one more thing, could you please also re-play .trace from that old issue, > and say whether you see an issue or not. If you see it... I may suppose, > that somehow in your environment mesa was downgraded Trace file from bug: 100790 renders with blue glitches. Where to search help? At least I will install native Steam (not flatpaked) and test.
Can this bug be related to shader cache? I remember that Intel shader cache was disabled and enabled, so maybe the bug was related to old cache. Why? I played via Steam on flatpak and next switch to rpm package and play on flatpak actually (again use flatpak).
Hello, Slawomir. Also checked with https://mesa.freedesktop.org/archive/mesa-18.0.4.tar.gz (that seems to be the latest version with flatpak) and works fine. So seems there is some issue with your runtime. ATM can't know exactly what is the reason, but could you try commnds and give us a results: 1. Check which runtimes contains needed dri: locate i956_dri.so | grep runtime You can observe a list of installed runtimes, such as: /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/1.6/some_path/i965_dri.so /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/1.4/some_path/i965_dri.so and so on 2. Check for each of them what is glxinfo returns, like: flatpak run --runtime=org.freedesktop.Platform/x86_64/1.6 org.freedesktop.GlxInfo -B flatpak run --runtime=org.freedesktop.Platform/x86_64/1.4 org.freedesktop.GlxInfo -B and so on 3. If you don't have installed org.freedesktop.GlxInfo, than try: flatpak remote-add gnome-buildbot http://sdkbuilder1.gnome.org/gnome-buildbot.flatpakrepo flatpak install gnome-buildbot org.freedesktop.GlxInfo
(In reply to Sergii Romantsov from comment #18) > Hello, Slawomir. > Also checked with https://mesa.freedesktop.org/archive/mesa-18.0.4.tar.gz > (that seems to be the latest version with flatpak) and works fine. > So seems there is some issue with your runtime. > > > ATM can't know exactly what is the reason, but could you try commnds and > give us a results: > > 1. Check which runtimes contains needed dri: > locate i956_dri.so | grep runtime > You can observe a list of installed runtimes, such as: > /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/1.6/some_path/ > i965_dri.so > /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/1.4/some_path/ > i965_dri.so > and so on > I don't have locate installed and don't wanna waste time to build cache. If you like I will install locate find /home/slawomir/.local/share/ -iname i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.freedesktop.Platform/x86_64/1.6/ea1a12e21086ec56bba0c83a6e97511109cb300cc9deb2dbb1e1e3e68d91aa65/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.gnome.Platform/x86_64/3.22/d44159b609a60910cc4ac6176bcac448ae1a964b81b1917598d6246ec1838d9d/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.gnome.Platform/x86_64/3.24/bcb47fddc2506d90c9cc2ff0516ae25132e40065590e13afe8752cf233cc6ed8/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.gnome.Platform/x86_64/3.28/e676fe7f94201a4350385a98a0e099963e1a5062ee63f5dae26e797ee57b4c41/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.gnome.Sdk/x86_64/3.22/7ec9b226b95c0d9cb1efbfbe24b439c85bac36dda7b36e1ce2d34299dbc0c75b/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.freedesktop.Sdk/x86_64/1.6/41cd175ff11098dd18e9d31c24e2aab38ab7542fc0b63a06cbf3ccc6adff7547/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.freedesktop.Platform.GL.default/x86_64/1.6/fefd42de91fd4d688febbb100895990a3dae272ec379adaf30dff10d8e08345f/files/lib/dri/i965_dri.so /home/slawomir/.local/share/flatpak/runtime/org.freedesktop.Platform.Compat32/x86_64/1.6/32bf865a6c7baab4f9ec7546de569b5e19e44e8f45fdc635dcd22a265e3776a3/files/lib/dri/i965_dri.so > 2. Check for each of them what is glxinfo returns, like: > flatpak run --runtime=org.freedesktop.Platform/x86_64/1.6 > org.freedesktop.GlxInfo -B > flatpak run --runtime=org.freedesktop.Platform/x86_64/1.4 > org.freedesktop.GlxInfo -B > and so on > flatpak list Odniesienie Opcje com.bladecoder.adventure-editor/x86_64/stable user,current com.skype.Client/x86_64/stable user,current com.valvesoftware.Steam/x86_64/stable user,current org.freedesktop.GlxInfo/x86_64/1.6 user,current org.gna.Warmux/x86_64/stable user,current org.mozilla.Thunderbird/x86_64/stable user,current pl.art.lach.slawek.apps.progress/x86_64/master user,current org.DolphinEmu.dolphin_emu.Locale/x86_64/stable user,runtime,partial org.freedesktop.Platform.Compat32/x86_64/1.6 user,runtime org.freedesktop.Platform.GL.default/x86_64/1.6 user,runtime org.freedesktop.Platform.VAAPI.Intel/x86_64/1.6 user,runtime org.freedesktop.Platform.ffmpeg/x86_64/1.6 user,runtime org.freedesktop.Platform/x86_64/1.6 user,runtime org.freedesktop.Sdk/x86_64/1.6 user,runtime org.gnome.Platform/x86_64/3.22 user,runtime org.gnome.Platform/x86_64/3.24 user,runtime org.gnome.Platform/x86_64/3.28 user,runtime org.gnome.Sdk/x86_64/3.22 user,runtime flatpak run --runtime=org.freedesktop.Platform/x86_64/1.6 org.freedesktop.GlxInfo -B name of display: :99.0 display: :99 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) Bay Trail (0xf31) Version: 17.2.7 Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.2 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Bay Trail OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.2.7 OpenGL core profile shading language version string: 4.20 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 17.2.7 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.2.7 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 > 3. If you don't have installed org.freedesktop.GlxInfo, than try: > flatpak remote-add gnome-buildbot > http://sdkbuilder1.gnome.org/gnome-buildbot.flatpakrepo > flatpak install gnome-buildbot org.freedesktop.GlxInfo So I have probably older Mesa installed (17.2.7).That's look odd. Game works and stop once I updated runtime or Steam application.
I see above that GL libs are installed in both freedesktop platform and in extension called GL_default. Maybe that's a problem?
I uninstall org.freedesktop.Platform.GL.default and everything works perfect. Probably this extension was installed automatically due to runtime update. Thank! What can I do to prevent such situations in future? Fill bug report to freedesktop? This bug wasn't related to Mesa (it isn't a regression, so I again thanks for help).
> Thank! You are welcome :) > What can I do to prevent such situations in future? Fill bug report to freedesktop? Probably, yes, its better to report issue to freedesktop. > This bug wasn't related to Mesa (it isn't a regression, so I again thanks for help). Please, than close this issue.
I selected invalid item from dropdown menu. Maybe better is not a bug? If it is, please change it for me!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.