<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Divinity: Original Sin Enhanced Edition(Native) crash on start" href="https://bugs.freedesktop.org/show_bug.cgi?id=93551#c56">Comment # 56</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Divinity: Original Sin Enhanced Edition(Native) crash on start" href="https://bugs.freedesktop.org/show_bug.cgi?id=93551">bug 93551</a> from <a class="email" href="mailto:darktjm@gmail.com" title="Thomas J. Moore <darktjm@gmail.com>"> Thomas J. Moore</a> <pre>(In reply to Thomas Crider from <a href="show_bug.cgi?id=93551#c55">comment #55</a>) > With this patch users should be able to just apply the patch to mesa and run > the game. No shim needed. You seem to have missed the purpose of the shim. It was not to fix the problems; mesa patches were provided for that (which I guess you have successfully reinvented; I haven't actually looked at your patch). It was to avoid having to patch mesa every time it updates with patches that would likely never make it upstream. Keeping a custom patch for a distro-maintained and supplied package is a pain, even on distros that support such things directly, such as gentoo (which I use). You will also find that getting support for user-patched packages is much more difficult, even if the patch has nothing to do with the issue. Mesa updates fairly regularly, but I've been using the same shim now for over 2 years without recompile or having to modify the launch script. Unless your patch has been accepted into upstream mesa, your solution makes things harder, rather than easier.</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>