<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Don't print: "Note: Buggy applications may crash, if they do please report to vendor"" href="https://bugs.freedesktop.org/show_bug.cgi?id=99715#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Don't print: "Note: Buggy applications may crash, if they do please report to vendor"" href="https://bugs.freedesktop.org/show_bug.cgi?id=99715">bug 99715</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>From our e-mail discussion: > This is an interesting question. There is a fairly good historical reason > why we have that message. For a while after DRI3 first came out, DRI3 > support in the X server and in some of the device-specific back-ends was > buggy from time to time and a lot of users turned it off. Even though it's > been stable for a year or two now, there are still a number of users who > have it explicitly disabled for one reason or another. > > Since the Vulkan WSI model doesn't work with DRI2, we have to return no > presentation support on those platforms. When that happens, the user's app > will fail to start or even crash with no obvious explanation as to why. > The warning exists to tell those users to go check their xorg.conf file to > make sure they have DRI3. This warning message, I believe, has saved us > from a lot of bug reports of "application X crashes on your driver" with > other people saying "works for me". > > Now, on a reasonably standard gaming setup with an i-series Intel CPU with > integrated graphics and a discrete AMD or NVIDIA card and where the X > server is running directly on the discrete card, this falls apart a bit. > In that case, we can't do WSI but that's ok because you can just run on the > discrete card. I'm not quite sure what to do in this case. We could, > potentially, add a better heuristic to try and detect if we're running on a > DDX that would never support DRI3 (such as the NVIDIA one) and only print > the error in that case. I think we probably need some sort of heuristic for determining whether the problem is just that we're running against an incompatible DDX or if it's an otherwise compatible DDX and they just don't have DRI3 enabled. I'm not 100% sure how we should do that. Maybe just detect DRI2 but not DRI3?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>