Description of problem: firefox on plasma5 via startx on mga7 doesnt get its toolbar buttons pressed (like the three-strips menu button). It works fine in JWM. Also tested in a new firefox profile. I am on the core i3 machine of http://www.shlomifish.org/meta/FAQ/#computers-specs .
I now checked it in a new user in startx and it happens in there as well.
Assignee: bugsquad => kdeCC: (none) => marja11
I should note that in this case, what I mean is that the toolbar buttons are there, but in KDE/plasma pressing them does nothing and does not pop up the right submenus/dialogues.
Do the toolbar icons change on mouseover?
CC: (none) => zen25000
(In reply to Barry Jackson from comment #3) > Do the toolbar icons change on mouseover? yes, they do.
Confirmed here on Firefox 57.0.1 & Plasma Desktop Some buttons work like: Home, Reload, Back, Forward, Bookmark's side menu or Extensions (if added). Does not work: Downloads, Collections, Main Toolbar Menu (three line) button, uBlock Origin etc and also that "behind the corner menu" button if you put there something.
CC: (none) => jyri2000
I can confirm it happens for me too (Plasma, latest Cauldron updates, has been happening since a couple weeks ago). What I believe happens is that the buttons (main menu, add bookmark, basically any button that brings up a non-system menu or pop-up) actually work, but the menus/pop-up windows are invisible: in fact, if I press Ctrl+D to bookmark a page, even if no pop-up window is shown, when I press Enter the bookmark is saved correctly
CC: (none) => ita84
Sorry, forgot to mention this only happens when compositing is on; if I disable compositing with Alt+Shift+F12 the menus are shown correctly
Or leave compositing on, but choose XRender as compositing backend - all Firefox toolbar buttons are working OK in this case too. Seems to be somehow related to bug 22074, where Plasma panel color is wrong when compositing is on and backend is OpenGL 2.1 or 3.0...
With the latest Cauldron updates the bug has disappeared for me; I don't know which package it was though (probably Mesa), because of the recent mirror issues
(In reply to Davide Nifosi from comment #9) > With the latest Cauldron updates the bug has disappeared for me; I don't > know which package it was though (probably Mesa), because of the recent > mirror issues thanks, let me try.
Yes, seems to be fixed with latest cauldron updates as is bug 22074...
Seems to work fine here as well now. Resolving.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED