https://bugs.freedesktop.org/show_bug.cgi?id=110137
Bug ID: 110137 Summary: drirc adaptive sync, vrr, freesync blacklisting documentation Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: grmat@sub.red QA Contact: dri-devel@lists.freedesktop.org
Hi,
using qutebrowser in fullscreen mode breaks the video output with VRR enabled because it refreshes very unsteadily, which is typical for a browser. Some browsers are blacklisted in the drirc. I've added the following lines to the drirc, but it doesn't disable VRR for a fullscreen qutebrowser window.:
<application name="qutebrowser" executable="qutebrowser"> <option name="adaptive_sync" value="false" /> </application>
Is there any documentation about how the matching works?
https://bugs.freedesktop.org/show_bug.cgi?id=110137
--- Comment #1 from Nicholas Kazlauskas nicholas.kazlauskas@amd.com --- AFAIK, the matching should just be done based on the executable name.
See: src/util/u_process.c
The process name likely differs for the content processes for the browser. You might need both qutebrowser and QtWebEngineProcess blacklisted:
<application name="qutebrowser" executable="QtWebEngineProcess"> <option name="adaptive_sync" value="false" /> </application>
<application name="qutebrowser" executable="qutebrowser"> <option name="adaptive_sync" value="false" /> </application>
https://bugs.freedesktop.org/show_bug.cgi?id=110137
--- Comment #2 from grmat@sub.red --- Neither qutebrowser nor QtWebEngineProcess worked. Now I've seen that qtbrowser is built on PyQt5, so the executable name has to be "python3", this works:
<application name="qutebrowser" executable="python3"> <option name="adaptive_sync" value="false" /> </application>
I'd send in a patch for that, but I think this will block any python3-based app, which is not the goal here.
https://bugs.freedesktop.org/show_bug.cgi?id=110137
--- Comment #3 from Nicholas Kazlauskas nicholas.kazlauskas@amd.com --- I suppose that the issue with using realpath is while it's good at stripping args from chromium based browsers it'll have issues with programs run under script interpreters.
Maybe the drirc needs a more advanced app path or name matching method to deal with cases like that.
https://bugs.freedesktop.org/show_bug.cgi?id=110137
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #4 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1381.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org