Processed: affects 979590

Processing commands for cont...@bugs.debian.org: > affects 979590 + chromium Bug #979590 [libx11-xcb1] libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome Added indication that 979590 affects chromium > thanks Stopping processing here. Please contact me if you need

Bug#979590: libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome

Package: libx11-xcb1 Version: 2:1.7.0-1 Severity: normal X-Debbugs-Cc: mic...@lebihan.pl Dear Maintainer, After updating libx11-xcb1 chromium and google chrome UI is not responding to any input and clicking anywhere on the app window causes the GNOME app is not responding dialog to appear. The

Re: [Git][xorg-team/lib/mesa][debian-unstable] rules: Disable vulkan swrast, it's getting used instead of the native driver.

Ack. I agree with all what you wrote. On Fri, 8 Jan 2021 at 14:58, Michel Dänzer wrote: > > On 2021-01-08 11:22 a.m., Witold Baryluk wrote: > > True, that a lot of applications don't properly inspect physical devices > > list. > > (I do have some patches to various tools and examples to fix

Re: [Git][xorg-team/lib/mesa][debian-unstable] rules: Disable vulkan swrast, it's getting used instead of the native driver.

On 2021-01-08 11:22 a.m., Witold Baryluk wrote: True, that a lot of applications don't properly inspect physical devices list. (I do have some patches to various tools and examples to fix it, they are already in review by respective projects). Thanks for doing that, though I'm afraid it's a

Re: [Git][xorg-team/lib/mesa][debian-unstable] rules: Disable vulkan swrast, it's getting used instead of the native driver.

True, that a lot of applications don't properly inspect physical devices list. (I do have some patches to various tools and examples to fix it, they are already in review by respective projects). And it is also correct, that the order might be somehow random, i.e. depended on file system readdir