Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

Latest Update Broke the Opera UI

  • The use of right click and his menu is mandatory for me, so maybe i come back the day they fix that.. i don't use many of the fancy option and features of opera.

  • Hello,

    Whenever I right click anything in this browser, the menu that is supposed to come up is simply invisible. And I mean invisible, I can click it but can't see it.

    Not only that, but it seems that other pop up menus are affected as well.
    For example, when clicking the 3 dots here the menu is invisible too. I can click it, and whatever my cursor randomly lands upon will work, but I can't see what I'm clicking.
    fae8a24b-7ca8-4877-a9ea-ecf2b7957d5b-image.png

    Any help will be greatly appreciated!

  • Yep, same issue as all of you. Enabling hardware acceleration doesn't work, I guess I'm gonna install a previous version 😕

  • Just for the kicks, stable version 71.0.3770.198 doesn't solve the situation, still having all popup menus hidden to the naked eye, but the mouse can click on them and trigger actions.

  • Given I don't expect the fastest of resolutions, I went ahead and downgraded to 70.0.3728.95 (available here) and I got all pop-up menus back.

    For those that hardware acceleration is not an option, this is the alternative for now, I guess. Hope this helps.

  • @davidrmf

    Thanks, David. Downgrading is really the only choice for most users. Personally, I've never seen a browser release that literally kills the main functionality of itself before.

    And then updates follow that do not fix the issue.

    It is really bizarre. It isn't some minor issue like not being able to access history or maybe a new tab not closing or something.

    It's the main Opera menu and right click context menu functionality that is trashed and Opera can't seem to find a resolution for it. It has nothing to do with Chrome because, as we all know, Chrome isn't Opera.

    I don't know. Maybe the developers of Opera have just encountered an issue that they aren't educated or intelligent enough to fix. It could happen, you know. If no one working on Opera is smart enough to fix something, who is going to do it?

    The problem may never be corrected, which would be sad.

  • @minivan said in Latest Update Broke the Opera UI:

    @pyromantiker Even with this bug, things are much better in Opera than they are in firefox. Honestly, if you were really going to switch, then you'd switch. And if you were looking for a reason to not switch, then you found one. I doubt that this specific issue is the reason you'd not make the switch. It will get fixed in a matter of days, not a year. I'm sure you weren't trying to troll, but your comment reads that way.

    Hang on a second; let me make sure I understand this. You just called a poster a troll that said he would wait before using Opera after reading post after post after post after post about how Opera doesn't work properly.

    People are complaining and looking for solutions in every other thread. Opera doesn't work any longer. And here you are calling someone who thinks he will wait until things are worked out before switching to Opera a troll?

    If anyone is trolling, it is you. What you said to this poster doesn't make sense. Why would someone willingly install a browser that doesn't work? That would be idiotic.

  • @vr51

    Thanks, VR51. It's odd. The labels on the Speed Dial categories and the text on the Speed Dial entries are very large and all merge into one another. This issue was never an issue before upgrading to 71, just like the other problems.

    I thought maybe it was the same for everyone. Thanks for responding with the information you provided.

  • Heads up.
    I thought (foolishly) that I would give Opera Beta a try only to find no access to any menu at all. No settings etc. Any attempt to uninstall/remove has resulted in failure and the following message:

    Detailed errors from the package manager follow:

    snapd operation finished with error cannot perform the following tasks:

    • Save data of snap "opera-beta" in automatic snapshot set #6 (cannot create archive: tar: 79/.config/opera-beta/oauc_pipe: socket ignored (and 31 more))
  • @rob-bob-dave
    Update:
    dpkg --list
    shows no sign of opera-beta or opera to uninstall through the command line

  • @rob-bob-dave

    Snaps are self contained packages. There is nothing installed when you use a snap.

    Try to install from the repo. Add this line to your sources

    deb https://deb.opera.com/opera-beta/ stable non-free
    

    See here for Snapcraft (Snaps): https://snapcraft.io/opera-beta

    See here for .deb packages https://www.opera.com/computer

    See here for Opera Beta .deb packages https://www.opera.com/computer/beta

    Click the big blue download button, not the snap/rpm links.

  • 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 🙂

  • 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.

  • 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.

  • @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)

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

  • 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

  • @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?

  • @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.

  • 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).