[Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation

2019-09-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110137 GitLab Migration User changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation

2019-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110137 --- Comment #3 from Nicholas Kazlauskas --- 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

[Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation

2019-04-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110137 --- Comment #2 from gr...@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: I'd send in a patch for that, but I think

[Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation

2019-03-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110137 --- Comment #1 from Nicholas Kazlauskas --- 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

[Bug 110137] drirc adaptive sync, vrr, freesync blacklisting documentation

2019-03-15 Thread bugzilla-daemon
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