Posts made by annoyed-at-updates

@marinaz909 Hello,

I wanted to check in to see if there had been any follow-up on this issue in the last couple weeks.

Thank you for your time and attention with this matter,
"Annoyed-At-Updates"

Any word on what's going on here?

Problem: Opera updates can have unintended effects - some minor, some major. An easy fix is to go back to the previous update - but this is only temporary, since Opera's design forces the browser to update again, effectively re-imposing the problematic update.

Suggestion: on "Update & Recovery," give the user the option to "pause automatic update until next version."

E.g. I'm currently having issues with 119.0.5497.70 on Opera One. All of my issues are immediately solved by reverting to 119.0.5497.56 - and I should be able to pause automatic updates until Opera has an update after 119.0.5497.70.

This seems like a fair compromise to me. There is a part of me, however small, however reluctant, that understands how Opera needs to keep Users updated & on the same page. At the same time, I as the user should be able to protect my own device from updates that harm my experience of the browser.

So instead of an indefinite "forever" pause, let's just pause on this one update that's not working - then when there's the next update, I as the user have to at least give that update a chance.

This doesn't work. It triggers a playback error on YouTube, stopping any video from playing.

Ad Block Plus actually works; this one doesn't. What was the process for testing? Here's the error message I get every single time when using this add-on:

@Aminchen Which version number are you on? Is it the one ending in .70?

I had a similar problem with Opera One, the latest "stable update" ending in 70, and that problem (and multiple other issues) went away immediately as soon as I reverted back to the update ending in .56.

@leocg Here are the crash ID's that don't say "Discarded=1":

Opera One -

bp-7aa5a25f-6e14-4ac4-a0db-19ab70250609
bp-70d93de6-36f9-493d-bf88-7d4ec0250608
bp-d13abbac-f5f2-4f84-ab50-7e96a0250607
bp-d2586895-5bde-4270-8568-1de6b0250607
bp-ddcc8366-1b7f-40fe-bcd9-f2d540250606

Opera GX -

bp-30387640-6d17-41dc-a61e-4c3f10250610
bp-f3e62531-fb32-41d3-9ded-0f5260250610
bp-368bc00e-226a-498a-a06b-0a7800250610

@marinaz909 I really appreciate the response, especially since I'm not particularly proud of how snarky I got in my post.

Crash ID - the thing is, there isn't a crash ID, singular. There's 5 1/2 pages of crash ID's after I printed opera://crashes to PDF. Is there some way I could send you that document?

Opera version: I'm having this problem on both 119.0.5497.70 (Opera One) and 119.0.5497.78 (Opera GX).

Operating System: Windows 11

EDIT: I can also confirm that this issue does not exist for the previous stable version of Opera One (119.0.5497.56). I reverted back to that state. However, as you well know, Opera insists on forcing the updated version on me, so by the time I wake up tomorrow, it will have re-updated to the unusable 119.0.5497.70 version.

I'm reaching out about a critical issue I've encountered with Opera GX. It's the same issue as with Opera One: ever since a recent update, the browser quickly becomes overwhelmed whenever I'm on a video call, and crashes due to being 'out of memory.' Afterward, Opera GX fails to detect the camera.

This issue persists even after troubleshooting steps like reinstalling the camera device.

Notably, other browsers like Edge and Vivaldi do not have this problem, and the camera works fine in other applications.

Given that this issue started after an update, I'm concerned about the impact on usability. Opera is my #1 browser whenever it works, but this new issue is making all current versions of the browser unusable for me at the moment.

@leocg For the record, the same problem is also happening on Opera GX.

@leocg The one that's just labeled "Opera."

Latest update crashes on Google Meet video calls. When browser auto-recovers, my camera is switched off and the browser will not recognize the camera until I restart the browser.

I was not having this problem until ~24 hours ago. I am not having this problem on any other browser.

FYI to development team: video calls exist. I'm finding that when y'all roll out new updates, video calls are routinely the "canary in the coal mine" where issues pop up. If you're going to jam updates down my throat, at least do the common courtesy of ensuring the new update is functional with mainstream use cases.

@Freeheelpete That's great that you found a fix!

I've done a couple updates to all versions of Opera on my desktop PC, and haven't had any success, so my only fix so far has been to conduct all banking on another browser.

@annoyed-at-updates
I also want to add that I'm having this problem on multiple devices, tried clearing cache, etc.

@leocg Opera One. I haven't used GX in quite some time, and I'm not familiar with the other one you mentioned.

It's like the bank is specifically blocking log-in attempts from this one browser.

When using the Opera browser, I am unable to log in to my bank account with Wells Fargo using the correct username and password.

I've been able to log in on Edge & Vivaldi using the exact same username & password. (Wells Fargo lists Edge as a supported browser, while Vivaldi is not listed as one).

This is the first version of Opera in a few months where I can reliably make calls on Google Meet without it crashing the browser. I'm in a long-distance relationship, so being able to sustain a Google Meet call is necessary for a browser to be usable for me. Thank you so much for correcting that issue and making the browser as stable and reliable as I had known it to be.

@kshitizreturns complained, yes; solution, no. I'm using different browsers, and keeping an eye out for if/when these recent issues with Opera get resolved.

@AnChill said in Do amazing things with tabs in Opera browser – split, trace, and decorate:

@annoyed-at-updates: if you move tabs to an additional window just to create a split screen there's a chance of losing every open tab you had open. Power goes out, you close the "main" window without previously closing the temporary one, and now everything is gone. If there are tabs you haven't opened in a while they might not even show up in history for the last time you opened the browser. As for drag & separate - just release the tab above the address bar area, it's really not that hard to figure it out

Two thoughts:

1 - I didn't state it in this thread, but my main complaint with this new tab-splitting feature in Opera is that it's introduced a new instability into the browser that wasn't there before. Ever since Opera introduced this feature, now any attempt to move or manipulate a tab with a Google Meet call immediately crashes the browser.

2 - We just have different experiences. I'm not sure how to account for that, I just know that my experience isn't the same as yours in a couple ways that are relevant:

-Releasing the tab above the address bar, like you suggested, has only worked for me if I turn off the split tabs feature in Opera.

-I've never had a situation where I visited a site, and it didn't show up on my history unless I specific set up the browser not to include it in my history - and I've never had a site removed from my history simply by dragging a tab or splitting the screen, etc. In other words, if I've ever had my computer go out for whatever reason while using two windows on split screen, I've always been able to restore my session by identifying the sites I was on as separate entries in my history.

@besik33 I appreciate that suggestion! I personally stay away from mouse gestures, because they're too easy to trigger inadvertently when I don't want them - but they're a good option to have available to turn on or turn off, depending on how precise you are with your motions and/or how precise/reliable your pad is.