[Solved]45.0.2545.0 why depending compositing?
-
alexs last edited by
hey, the problem with the menu is another known bug, so we will be fixing it.
I hope, the build 46.0.2573.0 is the fifth dev build with the regression bug…
I downgrade again to 45.0.2539.0
-
A Former User last edited by
Please do something about it. I was on opera developer until it reached version 45 and compositing messed up the menus. Then I moved to opera beta which was on version 44. When opera beta was updated to version 45 and the compositing problem was not solved, I moved to opera stable whuch is on version 44 now.
If the problem exists by the time version 45 reaches stable, I will move to another browser.
Debian testing x64 with openbox and with no compositing.
-
A Former User last edited by admin
Opera 45 has reached rc today and neither the compositing problem, nor the dark theme problem* are solved yet, so I guess I should start looking for a new browser...
-
alexs last edited by
Yes, I also believe that it will be time for me to change to Vivaldi. The Opera Devs ignore this bug and this is also in the current Opera-Beta (45.0.2552.634) inside the soon to change stable.
I have spent a long time (since Opera 6.06) with Opera, it's time to go.
-
A Former User last edited by
I won't switch to vivaldi though. I really hate nodejs-based (or electron) apps. I may switch to qupzilla. It has switched to chromium engine since version 2, it has opera's 12.x speed dial, built in adblock and it looks quite promising
-
A Former User last edited by
Opera 45 reached stable a few minutes ago and neither the dark theme bug, nor the compositing one was solved. Goodbye opera.
-
A Former User last edited by admin
Same here with mate and mint 18.1 with disabled compositing:
https://forums.opera.com/topic/20584/black-border-around-context-menus
-
pvozerski2 last edited by
I confirm the "ugly border" bug on LMDE 2 with Trinity DE R14.0.4 installed.
-
maxymku last edited by
Other method: opera://settings/ => Browser => System => disable "Use hardware acceleration when available".
-
parkmino last edited by
@maxymku
opera://flags/?search=overr#ignore-gpu-blacklist and the another preferences does not help.
Only enable the compositing manager…Both methods solve the effect of "big ugly black border" in my system (Slackware 14.0, x86).
This workaround does not apply to lubuntu 16.04 amd64
-
A Former User last edited by
None of these workarounds worked for me as well (debian testing x64, openbox, no compositing manager, opera 45 stable).
Since the lazy maintainers of my disto have not yet packaged qupzilla 2.1.x, I am back to opera. And reopened my account here, because deleting it would also delete my comments
-
jskier last edited by
Also present on Arch Linux. Have tested Intel, AMD, and Nvidia gpu; if compositing is off these borders show up.
https://bugs.archlinux.org/task/54005?project=5&cat[0]=33&string=opera
-
A Former User last edited by
The compositing bug was solved today in the latest opera-developer version, along with the dark theme one.