https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240097
--- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: adridg Date: Sun Jul 19 13:38:27 UTC 2020 New revision: 542576 URL: https://svnweb.freebsd.org/changeset/ports/542576 Log: Remove mention of a command-line-flag that doesn't work. There is a discussion of these flags in qutebrowser's bugtracker (not otter!), https://github.com/qutebrowser/qutebrowser/issues/2671 but the mechanism of "--qt-flag" is specific to qutebrowser: it isn't a general Qt thing. I can't find anywhere in otter-browser's source history where it has a --disable-gpu flag: that **is** a Qt thing, as documented at https://doc.qt.io/qt-5/qtwebengine-debugging.html However the application has to be able to pass that on to Qt (which otter apparently doesn't anymore, and neither does falkon). Overall the recommendation is to use environment variables to manage Chromium-inside-WebEngine, as documented by Qt, e.g. QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" otter-browser PR: 237277 240097 Changes: head/www/otter-browser/pkg-message -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
