Skip to content
Snippets Groups Projects
Commit 29c758a1 authored by Sébastien Blin's avatar Sébastien Blin
Browse files

qtwebengine: remove no-sandbox flag

In 64720224, a no-sandbox flag was
added because QtWebEngine can't load fonts on recent glibc. Source:
https://bugreports.qt.io/browse/QTBUG-92969
https://bugs.chromium.org/p/chromium/issues/detail?id=1164975

Now, we use Qt 6.2, so this flag should not be necessary.
So, we can finally close #442 without any dirty workaround.

GitLab: #442
Change-Id: I52835e40d37d2397a891415fd2b1dd8dd4048b8b
parent 16424e53
No related branches found
No related tags found
No related merge requests found
......@@ -51,7 +51,6 @@ parseInputArgument(int& argc, char* argv[], QList<char*> argsToParse)
}
// Qt WebEngine Chromium Flags
static char noSandbox[] {"--no-sandbox"};
static char disableWebSecurity[] {"--disable-web-security"};
static char singleProcess[] {"--single-process"};
......@@ -77,14 +76,6 @@ main(int argc, char* argv[])
* https://bugreports.qt.io/browse/QTBUG-99889
*/
unsetenv("QT_STYLE_OVERRIDE");
#ifdef __GLIBC__
// Current glibc is causing some bugs with font loading
// See https://bugreports.qt.io/browse/QTBUG-92969
// As I prefer to not use custom patched Qt, just wait for a
// new version with this bug fixed
if (__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 33))
qtWebEngineChromiumFlags << noSandbox;
#endif
#endif
qtWebEngineChromiumFlags << disableWebSecurity;
qtWebEngineChromiumFlags << singleProcess;
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment