Summary: | www-client/firefox-47.0.1[hwaccel]: unresponsive UI in Plasma5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daiajo Tibdixious <daiajo> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daiajo Tibdixious
2016-08-07 23:36:19 UTC
(In reply to Daiajo Tibdixious from comment #0) > Ever since the KDE5 upgrade, firefox has been behaving very oddly. This problem occurs in Plasma-5 session, right? Is this problem reproducible outside of KDE session? > I am willing to fiddle with USE flags, I just don't know which one applies, > I suspect "hwaccel". 'hwaccel' indeed enables 'layers.acceleration.force-enabled' option. Try disabling this USE flag. In my user account, after doing startx, firefox does not start. A window appears called "untitled" and it just sits there. I'm using chromium at the moment. This error does appear in the console (xterm) Can't find symbol 'EGLImageTargetRenderbufferStorageDES'. repeated twice (not that I typed that in, its not a copy/paste). I am going to proceed rebuilding firefox with -hwaccel in package.use I just realized I put firefox on ~amd64, thinking the latest version might be better, I'll regress it to the stable version and retest. Well the version I was using has become stable, so I just rebuild it with ~amd64 removed and hwaccel still there. The rebuild version had the same problem, it would not start within xterm. Added the -hwaccel use flag & rebuild it, now firefox starts within xterm and is stable. I tried the most harsh app which always failed: cookieclicker, which is now running fine. So it may have been a coincidence that this happened at the same time as the kde5 upgrade. I see. This is most likely the same issue as bug 569036, since you have that "Can't find symbol 'EGLImageTargetRenderbufferStorageOES'" error and similar problems. *** This bug has been marked as a duplicate of bug 569036 *** |