mirror of
https://git.jami.net/savoirfairelinux/jami-client-qt.git
synced 2025-08-04 06:45:45 +02:00
qtwebengine: remove no-sandbox flag
In 64720224eb
, 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
This commit is contained in:
parent
16424e530a
commit
29c758a141
1 changed files with 0 additions and 9 deletions
|
@ -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;
|
||||
|
|
Loading…
Add table
Reference in a new issue