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: Re%3A Bug#874715 mesa Games like Counter-Strike Global Offensive dont%0A start after upgrading mesa to 17.2.0-2
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 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
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)
Bug#796291: md5deep: No executable found
Package: md5deep Version: 4.4-2 Severity: grave Justification: renders package unusable I cant find any executables after installing md5deep. Displaying all installed files from this package only shows some documentation files: dpkg -L md5deep /. /usr /usr/share /usr/share/doc /usr/share/doc/md5deep /usr/share/doc/md5deep/changelog.Debian.gz /usr/share/doc/md5deep/changelog.gz /usr/share/doc/md5deep/copyright Regards, Dominik Kupschke -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages md5deep depends on: ii hashdeep 4.4-1 md5deep recommends no packages. md5deep suggests no packages. -- no debconf information
Bug#775175: congruity: Unable to login with mhgui or executing EZHex Files because of changes in the MyHarmony website.
Hi Scott, I use an Harmony 300, but this error also occurs without any remote attached. Dominik Am 15.01.2015 um 14:54 schrieb Scott Talbert: Hi Dominik, What model of remote are you using? Scott On Thu, 15 Jan 2015, Dominik Kupschke wrote: Hi Scott, I got this message in my terminal: Unhandled exception in thread started by bound method BackgroundTask.ThreadFunction of __main__.BackgroundTask instance at 0x7f2933402b48 Traceback (most recent call last): File /usr/bin/mhgui, line 124, in ThreadFunction result = self.backgroundFunction(*self.backgroundFunctionArgs) File /usr/bin/mhgui, line 252, in DoLogin return mhMgr.Login(username, password) File /usr/share/congruity/mhmanager.py, line 162, in Login isPresistent=False) File /usr/lib/python2.7/dist-packages/suds/client.py, line 542, in __call__ return client.invoke(args, kwargs) File /usr/lib/python2.7/dist-packages/suds/client.py, line 602, in invoke result = self.send(soapenv) File /usr/lib/python2.7/dist-packages/suds/client.py, line 647, in send result = self.succeeded(binding, reply.message) File /usr/lib/python2.7/dist-packages/suds/client.py, line 684, in succeeded reply, result = binding.get_reply(self.method, reply) File /usr/lib/python2.7/dist-packages/suds/bindings/binding.py, line 151, in get_reply self.detect_fault(soapbody) File /usr/lib/python2.7/dist-packages/suds/bindings/binding.py, line 182, in detect_fault raise WebFault(p, fault) suds.WebFault: Server raised fault: '1' Dominik Am 13.01.2015 um 02:57 schrieb Scott Talbert: Hi Dominik, What error(s) specifically are you seeing? I'm able to log on just fine using the version in unstable (which has the sme version). Scott -- Dominik Kupschke Mobil:+49-1522-3044310 Website:http://kupschke.net E-Mail: domi...@kupschke.net Xing:https://www.xing.com/profile/Dominik_Kupschke/ LinkedIn: https://www.linkedin.com/pub/dominik-kupschke/90/110/525 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775175: congruity: Unable to login with mhgui or executing EZHex Files because of changes in the MyHarmony website.
Hi Scott, I got this message in my terminal: Unhandled exception in thread started by bound method BackgroundTask.ThreadFunction of __main__.BackgroundTask instance at 0x7f2933402b48 Traceback (most recent call last): File /usr/bin/mhgui, line 124, in ThreadFunction result = self.backgroundFunction(*self.backgroundFunctionArgs) File /usr/bin/mhgui, line 252, in DoLogin return mhMgr.Login(username, password) File /usr/share/congruity/mhmanager.py, line 162, in Login isPresistent=False) File /usr/lib/python2.7/dist-packages/suds/client.py, line 542, in __call__ return client.invoke(args, kwargs) File /usr/lib/python2.7/dist-packages/suds/client.py, line 602, in invoke result = self.send(soapenv) File /usr/lib/python2.7/dist-packages/suds/client.py, line 647, in send result = self.succeeded(binding, reply.message) File /usr/lib/python2.7/dist-packages/suds/client.py, line 684, in succeeded reply, result = binding.get_reply(self.method, reply) File /usr/lib/python2.7/dist-packages/suds/bindings/binding.py, line 151, in get_reply self.detect_fault(soapbody) File /usr/lib/python2.7/dist-packages/suds/bindings/binding.py, line 182, in detect_fault raise WebFault(p, fault) suds.WebFault: Server raised fault: '1' Dominik Am 13.01.2015 um 02:57 schrieb Scott Talbert: Hi Dominik, What error(s) specifically are you seeing? I'm able to log on just fine using the version in unstable (which has the sme version). Scott -- Dominik Kupschke Mobil: +49-1522-3044310 Website:http://kupschke.net E-Mail: domi...@kupschke.net Xing: https://www.xing.com/profile/Dominik_Kupschke/ LinkedIn: https://www.linkedin.com/pub/dominik-kupschke/90/110/525 signature.asc Description: OpenPGP digital signature
Bug#775175: congruity: Unable to login with mhgui or executing EZHex Files because of changes in the MyHarmony website.
Package: congruity Version: 18-1.1 Severity: grave Justification: renders package unusable Possible fix can be found in following commit: http://sourceforge.net/p/congruity/code/ci/e80d7c73494618182ea26325cac66c3e375b82e4/ -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages congruity depends on: ii python [python-ctypes] 2.7.8-2 ii python-libconcord 1.1-2 ii python-suds 0.4.1-15 ii python-wxgtk3.0 3.0.1.1+dfsg-2 ii shared-mime-info1.3-1 congruity recommends no packages. congruity suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
