Skip to content
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

Closed
The-Compiler opened this issue Jan 3, 2018 · 12 comments
Closed

"Failed to open file" warning with Qt 5.10 #3459

The-Compiler opened this issue Jan 3, 2018 · 12 comments
Labels
component: QtWebEngine Issues related to the QtWebEngine backend, based on Chromium. priority: 2 - low Issues which are currently not very important.

Comments

@The-Compiler
Copy link
Member

The-Compiler commented Jan 3, 2018

After upgrading to Qt 5.10, I noticed this (with e.g. --temp-basedir):

[0103/104952.523679:WARNING:stack_trace_posix.cc(648)] Failed to open file: /home/florian/#14750431 (deleted)
  Error: No such file or directory

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-Compiler The-Compiler added component: QtWebEngine Issues related to the QtWebEngine backend, based on Chromium. priority: 2 - low Issues which are currently not very important. qt: 5.10 labels Jan 3, 2018
@lahwaacz
Copy link
Contributor

I'm also getting a similar warning:

[0116/133327.700515:WARNING:stack_trace_posix.cc(648)] Failed to open file: /tmp/.gl4KTWEs (deleted)
  Error: No such file or directory

See also the qutebrowser --version output in #3447.

@urbainvaes
Copy link

I'm also getting this warning, with this output of qutebrowser --version:

qutebrowser v1.1.1
Git commit: 
Backend: QtWebEngine (Chromium 61.0.3163.140)

CPython: 3.6.4
Qt: 5.10.1
PyQt: 5.10

sip: 4.19.7
colorama: 0.3.9
pypeg2: 2.15
jinja2: 2.10
pygments: 2.2.0
yaml: 3.12
cssutils: no
attr: 17.4.0
PyQt5.QtWebEngineWidgets: yes
PyQt5.QtWebKitWidgets: yes
pdf.js: no
sqlite: 3.22.0
QtNetwork SSL: OpenSSL 1.1.0g  2 Nov 2017

Style: QFusionStyle
Platform: Linux-4.15.5-1-ARCH-x86_64-with-arch, 64bit
Linux distribution: Arch Linux (arch)
Frozen: False
Imported from /usr/lib/python3.6/site-packages/qutebrowser
Qt library executable path: /usr/lib/qt/libexec, data path: /usr/share/qt

Paths:
cache: /home/urbain/.cache/qutebrowser
config: /home/urbain/.config/qutebrowser
data: /home/urbain/.local/share/qutebrowser
runtime: /run/user/1000/qutebrowser
system data: /usr/share/qutebrowser

In my case the browser does not open because of it. Is there a workaround to make it work?

@The-Compiler
Copy link
Member Author

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.

@The-Compiler
Copy link
Member Author

Someone else reported this upstream as QTBUG-68547.

@legallyrobert
Copy link

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.

@The-Compiler
Copy link
Member Author

It's a harmless warning.

@lahwaacz
Copy link
Contributor

lahwaacz commented Nov 5, 2018

And the upstream bug says "Fix Version/s: 5.12.0 Beta 1"...

@tallero
Copy link
Contributor

tallero commented Nov 5, 2018

What is the latest stable version of QtWebEngine?

@The-Compiler
Copy link
Member Author

@tallero that seems unrelated to this issue, and is something you could easily look up yourself (5.11.2)

@tallero
Copy link
Contributor

tallero commented Nov 5, 2018

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!
I think you can safely close the bug if it is corrected in a developer version of qtwebengine.

@The-Compiler
Copy link
Member Author

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. 😉

@tallero
Copy link
Contributor

tallero commented Nov 5, 2018

Sorry! I thought I could not post in closed bugs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: QtWebEngine Issues related to the QtWebEngine backend, based on Chromium. priority: 2 - low Issues which are currently not very important.
Projects
None yet
Development

No branches or pull requests

5 participants