Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Am Donnerstag, 14. Dezember 2017, 20:14:46 CET schrieb Andreas Boll: > Control: tag -1 moreinfo > > On Fri, Oct 13, 2017 at 10:24:19AM +0200, Andreas Boll wrote: > > Control: severity -1 important > > > > On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote: > > > Hi, > > > > > > I was able to start some steam games without steam-runtime. > > > Also non Steam Games work properly. > > > > > > Regards > > > Dominik > > > > Hi, > > > > so it looks like an issue with the steam-runtime. Please report this > > issue to Valve on github and let us know the bug number/url for > > tracking. > > > > I'm lowering the severity to important to let Mesa migrate to testing > > since it blocks lots of packages. > > > > Thanks, > > Andreas > > Is this still an issue with mesa 17.3.0? Did you report this issue to > Valve on github? > > Thanks, > Andreas > Hi, this is fixed in the latest steam package released by debian: https://tracker.debian.org/news/933866 Regards Dominik signature.asc Description: This is a digitally signed message part.
Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Control: tag -1 moreinfo On Fri, Oct 13, 2017 at 10:24:19AM +0200, Andreas Boll wrote: > Control: severity -1 important > > On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote: > > Hi, > > > > I was able to start some steam games without steam-runtime. > > Also non Steam Games work properly. > > > > Regards > > Dominik > > Hi, > > so it looks like an issue with the steam-runtime. Please report this > issue to Valve on github and let us know the bug number/url for > tracking. > > I'm lowering the severity to important to let Mesa migrate to testing > since it blocks lots of packages. > > Thanks, > Andreas Is this still an issue with mesa 17.3.0? Did you report this issue to Valve on github? Thanks, Andreas
Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Control: severity -1 important On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote: > Hi, > > I was able to start some steam games without steam-runtime. > Also non Steam Games work properly. > > Regards > Dominik Hi, so it looks like an issue with the steam-runtime. Please report this issue to Valve on github and let us know the bug number/url for tracking. I'm lowering the severity to important to let Mesa migrate to testing since it blocks lots of packages. Thanks, Andreas signature.asc Description: PGP signature
Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Hi, I was able to start some steam games without steam-runtime. Also non Steam Games work properly. Regards Dominik signature.asc Description: This is a digitally signed message part.
Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
On Fri, Sep 29, 2017 at 07:21:42AM +0200, Dominik Kupschke wrote:: > This issue affects all of my steam games (> 100), so the migration of the > packet to testing could be bad for a lot of people. Could it be a problem with Steam runtime? Their bundling is known to be messy, like conflicting libstdc++ which clashes with libgl1-mesa-dri (radeonsi_dri.so is using libstdc++, and if Steam runtime bundles it, it can easily break C++ ABI compatibility). Similar stuff can happen to other libraries. Basically, can you run any game without Steam runtime? Try some of the same games from GOG, which come without Steam runtime, or figure out how to run such game directly without Steam client and full runtime LD_LIBRARY_PATH. Since you you saying a lot of games are broken in the similar way, it's very likely Steam runtime is the culprit. If that is indeed the case, it's not really Mesa's or Debian's problem, and Steam runtime itself needs fixing. Regards, Hillel Lubman.
Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
On Fri, Sep 29, 2017 at 07:21:42AM +0200, Dominik Kupschke wrote: > Yes I am fine with changing the severity to important. > > This issue affects all of my steam games (> 100), so the migration of the > packet to testing could be bad for a lot of people. > > Regards > Dominik So does this issue affect only i386 games or steam games. Could you try some non-steam i386 games/benchmarks and some amd64 games/benchmarks? There's currently an issue with llvm not building on i386. Maybe that's somehow related. Could you attach the list of installed llvm packages? dpkg -l | grep llvm Thanks, Andreas signature.asc Description: PGP signature
Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Should such bugs be a blocker? Other games work fine with this Mesa. This stalls migration of the package to testing for a lot of people. Just for the reference, if you need a specific Mesa, you can always use older one locally (without touching the system wide package) and run some game with it. I don't think it's good to stall the package because of this for everyone else. The severity here should be probably important, not grave. Regards, Hillel Lubman.
Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
(Adding original bug reporter) Is this still an issue with mesa 17.2.1? Could the following be related to your issue? On Fri, Sep 15, 2017 at 08:01:54AM +0200, Gert Wollny wrote: > Since you are using radeonsi you may have a conflict between the system > libstdc++ and the one shipped with the steam runtime (Although this > usually meant Steam doesn't start at all). > > cf: https://github.com/ValveSoftware/steam-for-linux/issues/3273 Could you please attach the output from LIBGL_DEBUG=verbose glxinfo and if possible replace mesa-utils:amd64 with mesa-utils:i386 and run glxinfo again and attach its output too. Thanks, Andreas signature.asc Description: PGP signature
Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Since you are using radeonsi you may have a conflict between the system libstdc++ and the one shipped with the steam runtime (Although this usually meant Steam doesn't start at all). cf: https://github.com/ValveSoftware/steam-for-linux/issues/3273
Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Hi, i attach some additional information. These are all installed mesa packages on my system: ~$ dpkg -l | grep mesa ii libegl-mesa0:amd6417.2.0-2 amd64free implementation of the EGL API -- Mesa vendor library ii libegl-mesa0:i386 17.2.0-2 i386 free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd6417.2.0-2 amd64transitional dummy package ii libegl1-mesa:i386 17.2.0-2 i386 transitional dummy package ii libgl1-mesa-dev:amd64 17.2.0-2 amd64free implementation of the OpenGL API -- GLX development files ii libgl1-mesa-dri:amd64 17.2.0-2 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i386 17.2.0-2 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 17.2.0-2 amd64transitional dummy package ii libgl1-mesa-glx:i386 17.2.0-2 i386 transitional dummy package ii libglapi-mesa:amd64 17.2.0-2 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i38617.2.0-2 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 17.2.0-2 amd64transitional dummy package ii libglu1-mesa:amd649.0.0-2.1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd6417.2.0-2 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 17.2.0-2 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd64 17.2.0-2 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 17.2.0-2 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd6417.2.0-2 amd64implementation of the Wayland EGL platform -- runtime ii mesa-common-dev:amd64 17.2.0-2 amd64Developer documentation for Mesa ii mesa-common-dev:i386 17.2.0-2 i386 Developer documentation for Mesa ii mesa-opencl-icd:amd64 17.2.0-2 amd64free implementation of the OpenCL API -- ICD runtime ii mesa-utils8.3.0-5 amd64Miscellaneous Mesa GL utilities ii mesa-va-drivers:amd64 17.2.0-2 amd64Mesa VA-API video acceleration drivers ii mesa-va-drivers:i386 17.2.0-2 i386 Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 17.2.0-2 amd64Mesa VDPAU video acceleration drivers ii mesa-vdpau-drivers:i386 17.2.0-2 i386 Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 17.2.0-2 amd64Mesa Vulkan graphics drivers This is my Xorg.0.log: [ 11371.708] (--) Log file renamed from "/var/log/Xorg.pid-23713.log" to "/var/log/Xorg.0.log" Regards Dominik signature.asc Description: This is a digitally signed message part.
Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2
Source: mesa Version: 17.0.2-2 Severity: grave Justification: renders package unusable Hi, after upgrading mesa from 17.1.5 to 17.2.0-2 none of my games are able to start. At least Counter-Strike Global Offensive reports this failure back to me: Failed to create GL context: Could not make GL context current: GLXBadContextTag Regards Dominik -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
