From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [solved] Problem with qutebrowser (and only it) after Mesa upgrade
Date: Mon, 27 Dec 2021 04:57:59 +0100 [thread overview]
Message-ID: <20211227035759.lAvTwOGDt5aYMAJS90M_6sC3VQPydFsnRaUTbkJ8sxc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34674@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/34674#issuecomment-1001318370
Comment:
I had a chance to try the `MESA_LOADER_DRIVER_OVERRIDE` workaround (it isn't really a fix) on an Intel Xe device, and was met with errors reporting
```
gfx12 and newer are not supported on i965
libGL error: failed to create dri screen
libGL error: failed to load driver: i965
```
There were no glitches, but it seems Mesa fails entirely here. Thus, the workaround seems to be limited to older devices.
It seems that a proper fix may have been merged; maybe we can test a backport pending another upstream release.
next prev parent reply other threads:[~2021-12-27 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 6:54 [ISSUE] " intpl
2021-12-23 6:56 ` intpl
2021-12-23 14:02 ` ericonr
2021-12-23 14:37 ` ahesford
2021-12-23 21:45 ` jsbronder
2021-12-24 7:52 ` intpl
2021-12-24 11:40 ` [solved] " ahesford
2021-12-27 3:57 ` ahesford [this message]
2022-01-01 10:49 ` intpl
2022-01-01 11:22 ` intpl
2022-01-08 16:39 ` ardadem
2022-02-05 14:42 ` ericonr
2022-02-05 14:43 ` [ISSUE] [CLOSED] " ericonr
2022-02-05 14:43 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211227035759.lAvTwOGDt5aYMAJS90M_6sC3VQPydFsnRaUTbkJ8sxc@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).