[Solved]45.0.2545.0 why depending compositing?
-
alexs last edited by
With today developer build, i have on all menus a big ugly black border.
I have and i will not enable Compiz, never!Opera have option for Power saving mode/Battery saver, why i must enable the eye candy compositing?
Please add this as option (opera://flags), for me this is unacceptable.
Second:
On the right click menu on website the German word ›Über%tragen‹ (Inspect element) is wrong.
Correct: ›Übertragen‹OS: NVIDIA G94, Siduction x86_64 (based on Debian/sid) /Xfce
-
-
kmielczarczyk Opera last edited by
We were able to reproduce this only ones when running Opera for the first time. Then it was displayed properly. Maybe it's some site specific issue?
-
alexs last edited by
We were able to reproduce this only ones when running Opera for the first time. Then it was displayed properly. Maybe it's some site specific issue?
It's only a problem when disable compositing (for me Compiz under Xfce).
I have testing with clean Profile.
see the edit on the Dev Blog from user L33t4opera
-
-
-
A Former User last edited by
I can confirm this.
Opera 45.0.2548.0, using XFCE on Ubuntu 16.04.2 LTS. I don't use compiz, it is the composition of the own xfwm4, which can be adjusted using window manager settings. The black borders appears with composition disabled.
With composition enabled:
With composition disabled:
The dark theme bug deserves another post, I believe.
I have tested Opera 45.0.2548.0 on another system, this one with Ubuntu 16.04.2 LTS, LXDE, using openbox with no composition. It has the black borders too.
-
surf-ing last edited by
I can confirm this bug. GNU/Linux 64 box with OpenBox window manager and no video compositing manager (not even installed, will not install a compositing manager).
-
-
A Former User last edited by
hey, the problem with the menu is another known bug, so we will be fixing it.
-
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
-
-
-
