Summary: | drirc adaptive sync, vrr, freesync blacklisting documentation | ||
---|---|---|---|
Product: | Mesa | Reporter: | grmat |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | nicholas.kazlauskas |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
grmat
2019-03-16 02:18:46 UTC
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> 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. 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. -- 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. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.