New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Failed to open file" warning with Qt 5.10 #3459
Comments
I'm also getting a similar warning:
See also the |
I'm also getting this warning, with this output of
In my case the browser does not open because of it. Is there a workaround to make it work? |
That's most likely unrelated to the issue. I'd suggest you drop by in the IRC channel to track down what's happening. |
Someone else reported this upstream as QTBUG-68547. |
Is there any fix for this issue? I followed the issue upstream and found nothing. Trying to run on a fresh arch install, I've tried both building from source and pacman install. |
It's a harmless warning. |
And the upstream bug says "Fix Version/s: 5.12.0 Beta 1"... |
What is the latest stable version of QtWebEngine? |
@tallero that seems unrelated to this issue, and is something you could easily look up yourself (5.11.2) |
I asked because the upstream bug includes a patch which is included in 5.12 Beta 1. Since QtWebEngine apparently does not have its own official development page on which one can check the latest version page apart from this repo, which (is probably a mirror and) has both 5.12 and 5.12.0 branches, I was just wondering if I am just getting an old version from my distro. The repo even has a 5.11.3 branch! |
QtWebEngine is released together with Qt itself - the branches are for upcoming versions, you might want to look at the tags instead. The bug already is closed. 😉 |
Sorry! I thought I could not post in closed bugs! |
After upgrading to Qt 5.10, I noticed this (with e.g.
--temp-basedir
):It looks like it's coming from Chromium, but I'm not sure what causes it, I can't see it with e.g. QupZilla it seems?
Note: This is just a harmless warning which can be ignored - if you have some other issue, that's separate and unrelated to this warning.
The text was updated successfully, but these errors were encountered: