Latest Update Broke the Opera UI

[joklok]

joklok last edited by

Hello dear community,

I am using Opera with the current 71.0.3770.198 version. But since about 2 or 3 update I got these problems:

• Right-Clicking does not work, when I click with my right mouse button no menu appears. And opera kinda freezes, freez is gone when I switch tab or switch window with alt+tab
• The Opera-Menu doesn't open when I click on it
• when you have to many bookmarks there is a >> symbol on the right, which normaly shows the remaining bookmarks. Clicking on it doesn't work either
• when I am on the bookmarks page I can't use the button in the left bottom corner to backup the bookmarks

Are there others with the same problem?

Maybe some developer could look into this, for a fix in future updates.

Rest is running very good, well except the problem with libffmpeg.so (https://forums.opera.com/topic/30254/solved-video-playback-issues/7) but that is another story

Oh, and I use Fedora 32, if that info would be relevant.

Kind regards

[joklok]

joklok @joklok last edited by

Hoi,

I started Opera via terminal and got some information from there:

$ opera
[14507:1:1002/151111.492674:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14509:1:1002/151111.522605:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14528:1:1002/151111.549248:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14539:1:1002/151111.576064:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14540:1:1002/151111.593008:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14565:1:1002/151111.638200:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14588:1:1002/151111.814029:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14479:14487:1002/151128.756607:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720281
Xlib: sequence lost (0x102be > 0x2c0) in reply type 0x41!
[14479:14487:1002/151137.780813:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720284
[14896:1:1002/151208.922613:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14909:1:1002/151209.526865:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14919:1:1002/151209.790920:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14929:1:1002/151210.002817:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14947:1:1002/151214.648826:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14479:14487:1002/151221.587034:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720297
[14479:14487:1002/151226.787002:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720303
[14479:14487:1002/151229.134732:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720306
[14981:1:1002/151236.179970:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14986:1:1002/151236.186421:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[14479:14487:1002/151243.197061:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720321
[14479:14487:1002/151309.957573:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720324
[15022:1:1002/151311.215449:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer
[15023:1:1002/151311.217449:ERROR:child_thread_impl.cc(806)] Receiver for unknown Channel-associated interface: search.mojom.SearchBouncer

this seems to be interesting:

[14479:14487:1002/151128.756607:ERROR:x11_software_bitmap_presenter.cc(136)] XGetWindowAttributes failed for window 58720281

and this:

Xlib: sequence lost (0x102be > 0x2c0) in reply type 0x41!

Maybe someone with more experience could look into that.

[KetoKelo]

KetoKelo last edited by KetoKelo

I have been noticing that, the click-tab-to-go-to-page-top funcion is apparently being overwritten by the go-to-page-top button you can find in some sites. The only pages the function won't work are those that have this button. It really bothers me as these pages are mainly forums in which I constantly go up and down and I'm too much accustomed to this function. This isn't as much an attrocity as the problem with the menus, but they should correct it.

[brotherj4mes]

brotherj4mes @joklok last edited by

@joklok

Try enabling "hardward acceleration" in the settings menu. I had the same issue and this fixed it for me. (CentOS7; Opera71)

I found this issue and solution above (posted by KetoKelo)

[joklok]

joklok @brotherj4mes last edited by

@brotherj4mes Yep, enabling hardware acceleration helps, but this is a temporary fix.
Still thank you for your reply.

[davidhoff]

davidhoff last edited by

The same issue also for me (menu and right click). I use Linux Mint 20 Cinnamon. Thx to KetoKelo for solving. Works with hardware acceleration and Opera Beta. The same issue is present in Manjaro Cinnamon, Ubuntu Cinnamon and openSuse.

Linux Mint 20 Cinnamon
System: Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.6
wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 4024 date: 09/07/2018
CPU: Topology: 8-Core model: AMD Ryzen 7 1700X bits: 64 type: MT MCP arch: Zen rev: 1
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108581
Speed: 1882 MHz min/max: 2200/3400 MHz Core speeds (MHz): 1: 1882 2: 1892 3: 2674
4: 2255 5: 1717 6: 1879 7: 1711 8: 1705 9: 2033 10: 1888 11: 1882 12: 1886 13: 1882
14: 1891 15: 2465 16: 2654
Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nouveau v: kernel
bus ID: 09:00.0 chip ID: 10de:1c82
Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: NV137 v: 4.3 Mesa 20.0.4 direct render: Yes

[A Former User]

A Former User @Guest last edited by

@ctrlaltdel Not everyone experiences these issues and not everyone has problems with it. Most people would just go ahead and try it themselves for a day/week before deciding it. Its a free piece of software that you can easily install/uninstall along side any other browser. So yes, it (still) reads to me like the OP was looking for a reason to not try it. That is the troll part. Why bother posting that comment at all?

[A Former User]

A Former User @Guest last edited by

@minivan said in Latest Update Broke the Opera UI:

@ctrlaltdel Not everyone experiences these issues and not everyone has problems with it. Most people would just go ahead and try it themselves for a day/week before deciding it. Its a free piece of software that you can easily install/uninstall along side any other browser. So yes, it (still) reads to me like the OP was looking for a reason to not try it. That is the troll part. Why bother posting that comment at all?

The browser is broken; the only people not having issues with it are the people that likely already had hardware acceleration activated.

The poster you called a troll, for no reason, was merely stating that he was glad that he came and checked things out here before installing.

He wasn't promoting another browser, he wasn't insulting a specific operating system in favor of another operating system and he wasn't ridiculing Opera users.

He merely stated that he was happy that he didn't go ahead and install a broken browser before checking out the comments here. That is what this board is for, to help people.

He was helped by visiting here. No one is enough of a fanboy of any software, I don't think, to call someone a troll for refusing to use a product that is not currently working correctly.

Free or proprietary doesn't really matter for what is being discussed. Of course anyone can uninstall or not use any piece of software that they don't like. But, if anyone was trolling, it was you be being reactionary and feeling as if you had to be the defender of Opera's integrity.

[A Former User]

A Former User last edited by

I had the same problem. Everything worked fine until I updated Opera to 71.0.3770.148. I went back to version 70.0.3728.154 where this problem does not occur. My system is MX Linux (MX 19.2_x64 patito feo).

[KetoKelo]

KetoKelo last edited by

Version 71.0.3770.271. Still nothing.

[lovescience2011]

lovescience2011 last edited by

I can't use the mouse right-click function in the newest Linux version opera browser. Could you please solve this problem? Thank you very much.

[leocg]

leocg Moderator Volunteer @lovescience2011 last edited by

@lovescience2011 See above

[lovescience2011]

lovescience2011 @leocg last edited by This post is deleted!

[lovescience2011]

lovescience2011 last edited by

Hello, thank you very much for your help. I run Ubuntu 18.04 in VirtualBox. I enable hardware acceleration in the opera brwoser settings. But I still can't use the mouse right-click function in opera browser. How to solve this problem? Thank you so much for your help again.

[A Former User]

A Former User @KetoKelo last edited by

@KetoKelo - fixed it for me, thanks KetoKelo!

[davidrmf]

davidrmf @Guest last edited by

@metarhyme What did? Hardware acceleration or version 71.0.3770.271?

[A Former User]

A Former User @davidrmf last edited by

@davidrmf - in version 71.0.3770.271 turning on hardware acceleration terminates the bizarre behavior of no apparent right mouse click and so forth.

[davidrmf]

davidrmf last edited by

Just wanted to confirm. Actually, on all three versions since the problem started, turning Hardware Acceleration solves the situation. Basically, no changes in the most recent version. Unfortunately, turning that on is not an option for all of us. Thanks for replying.

[A Former User]

A Former User @davidrmf last edited by

@davidrmf said in Latest Update Broke the Opera UI:

Just wanted to confirm. Actually, on all three versions since the problem started, turning Hardware Acceleration solves the situation. Basically, no changes in the most recent version. Unfortunately, turning that on is not an option for all of us. Thanks for replying.

That's unfortunate. I got the Opera 72 update but thought I'd check here before going to the trouble of installing it, not having it work, and then having to rollback to Opera 70.

I was hoping that all the versions of 71 were going to be the only ones not working correctly and everything would be back to normal when Opera 72 arrived.

At this point, forcing you to turn on hardware acceleration or not being able to use the browser seems to just be a feature for Opera Linux users, not an error, and will never be changed.

It may be time to move on.

[vovan-ve]

vovan-ve last edited by

In my case hardware acceleration may randomly cause system crash like following while browsing a site. This bug related to Linux AMD graphic driver. This is Chromium bug since it the same for Opera and Vivaldi. I'm using both browsers every day and I intentionally disable hardware acceleration in Opera and enable in Vivaldi as longtime experiment.

As the result, the "hardware acceleration" option in Opera 71+ for me is now a switch between unusable UI and potential system crash. Keeping Opera 70 installed.