From: intpl <intpl@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Problem with qutebrowser (and only it) after Mesa upgrade
Date: Thu, 23 Dec 2021 07:54:29 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34674@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
New issue by intpl on void-packages repository
https://github.com/void-linux/void-packages/issues/34674
Description:
After system upgrade three days ago Qutebrowser started to behave terribly. Entire window become white for milliseconds, scattered parts of window. Pretty much unusable. Chromium and Google Chrome and Firefox which I have installed on the system all work fine. The issue is only with Qutebrowser. It worked perfectly fine before the upgrade.
I can see in the xbps log these 4 Mesa packages were updated (but also libglapi and libgbm which may also be related):
```
mesa-21.3.2_1
mesa-dri-21.3.2_1
mesa-intel-dri-21.3.2_1
mesa-vulkan-intel-21.3.2_1
```
This is my changed `/etc/modprobe.d/intel-graphics.conf`:
```
options i915 enable_dc=2 enable_fbc=1 fastboot=1
```
I use AwesomeWM if that's related.
next reply other threads:[~2021-12-23 6:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 6:54 intpl [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34674@inbox.vuxu.org \
--to=intpl@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).