> -Original Message-
> From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> On Behalf Of Kevin Mcintyre
> Sent: Tuesday, June 21, 2016 1:13 AM
> Cc: interest@qt-project.org
> Subject: Re: [Interest] linux 64 5.7.0 WebEngine segfault
>
> Ka
interest@qt-project.org
> > Betreff: [Interest] linux 64 5.7.0 WebEngine segfault
> >
> > When starting webengine - I get this error,
> >
> > [0617/091642:ERROR:browser_main_loop.cc(217)] Running without the SUID
> > sandbox! See
> > https://chromium.goo
Hi Kevin
> -Ursprüngliche Nachricht-
> Von: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> Im Auftrag von Kevin Mcintyre
> Gesendet: Freitag, 17. Juni 2016 18:23
> An: interest@qt-project.org
> Betreff: [Interest] linux 64 5.7.0 WebEngine segfault
Follow-up - segfault was the result of trying to use
QWebEngineUrlRequestInterceptor - a class I haven't been able to get
working.
On Fri, Jun 17, 2016 at 9:23 AM, Kevin Mcintyre wrote:
> When starting webengine - I get this error,
>
> [0617/091642:ERROR:browser_main_loop.cc(217)] Running withou
When starting webengine - I get this error,
[0617/091642:ERROR:browser_main_loop.cc(217)] Running without the SUID
sandbox! See
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md
for more information on developing with the sandbox on.
followed by this s