Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 672650

Summary: =dev-qt/qtwebengine-5.11.3 gets frozen when loading
Product: Gentoo Linux Reporter: David Roman <davidroman96>
Component: Current packagesAssignee: Qt Bug Alias <qt>
Status: RESOLVED FIXED    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description David Roman 2018-12-06 20:40:47 UTC
After upgrading Qt from 5.11.2 to 5.11.3 I was having some serious problems with qt applications that were using qtwebengine. Seems that when webengine is loaded the whole application gets frozen (for example qtcreator).

The next messages are printed to the console when the bug triggers:

[1206/213539.983649:ERROR:resource_bundle.cc(835)] Failed to load /usr/share/qt5/resources/qtwebengine_resources_100p.pak
Some features may not be available.
[1206/213539.983677:ERROR:resource_bundle.cc(835)] Failed to load /usr/share/qt5/resources/qtwebengine_resources_200p.pak
Some features may not be available.
Comment 1 Andreas Sturmlechner gentoo-dev 2018-12-06 20:56:15 UTC
Is that still in the same session you started with the upgrade? It is certainly not happening here.
Comment 2 David Roman 2018-12-06 21:30:29 UTC
(In reply to Andreas Sturmlechner from comment #1)
> Is that still in the same session you started with the upgrade? It is
> certainly not happening here.

No, I rebooted the computer. Maybe it's related with nouveau multi-threading issues?

I'm re-emerging all qt components including qtwebengine just in case.
Comment 3 David Roman 2018-12-06 23:09:08 UTC
(In reply to David from comment #2)
> (In reply to Andreas Sturmlechner from comment #1)
> > Is that still in the same session you started with the upgrade? It is
> > certainly not happening here.
> 
> No, I rebooted the computer. Maybe it's related with nouveau multi-threading
> issues?
> 
> I'm re-emerging all qt components including qtwebengine just in case.

It's fixed now, seems it was only a local problem.