@softer Идем в папку профиля C:\Users\ %UserName% \AppData\Roaming\Opera Software\Opera Stable\Local Storage\leveldb и в ней трем все файлы с расширением .ldb
Для профилактики еще можно сбросить синхронизацию и зайти заново на всех устройствах.

@max1c: Disabled opera://flags/#opera-account-popup

This version has been withdrawn. There has been no auto-update for 5 days, neither on FTP nor downloaded from the site Opera_116.0.5366.127_Setup_x64.exe They don't know what's going on anymore, bugs are just piling up, but they didn't forget to create another unnecessary browser in the form of Air instead of dealing with the main one.

@roverkvn
Надо делать сброс синхронизированных данных еще на всех устройствах. Но вообще могу от себя сразу сказать, что заниматься этим гемором придется постоянно, синхронизация вкладок не работает, а в Opera работают безрукие. Кроме закладок это никчемная синхронизация непригодна ни к чему.

Flow does not work on Opera for Android 61.2.3076.56749 Stable.
When you turn on Flow in sync, you are prompted to go to opera.com/connect and scan the QR code, but constantly displays the error "Unable to connect, Connection request was rejected on another device"

@max1c The old icon disappears some time after logging into the account.

How to remove it from the express panel

@kmielczarczyk: Competitors already have 131 finals, you even have a developer channel, the chrome version has not been updated for a month. You've been playing around with all sorts of decorative garbage, so that development at the level of a group of enthusiasts has begun to lag behind, and not a serious player in the browser market.

That the qualification does not allow updating the Chromium version. For the second month, the rotten 128 version.

@leocg The old 116 version is still swinging from the official website, and FTP is for those who know, I didn't notice it in the list, but it doesn't change the essence, the version has clearly been withdrawn, because there hasn't been an update for 5 days, but as always, no one will say directly, but they start telling tales about the gradual deployment of updates.

What's this crap that's appeared, and why can't I remove it? I click "Don't show again," but it reappears after opening a new tab or restarting the browser. They can't update the engine, but they still manage to shove in more junk.

@leocg: I already realized you're talking nonsense, or, like Opera, pretending not to understand what you're talking about. Chromium 144 should already be testing on the developer channel, so they can then move to the stable channel, as they did before, lagging behind by a couple of weeks. Now they're stuck on 140 and can't seem to make any progress.

@leocg: Opera's stable channel currently has Chromium: 140.0.7339.249. Where did you find 142? In a couple of days, 143 will be stable. Other developers are already testing 144 on their Dev channels. So, the question arises: why is Chromium still relevant in Opera, even on the Dev channel, where they're stuck on 140.0.7339.208?

@leocg: By the time they update to 141 or 142, their competitors will already be on 145 or 146. That's why one wonders what kind of mess is going on with Opera's developers, that they're unable to support the current engine and are lagging behind like some amateur startup. I'm not even talking about the slew of minor bugs that haven't been fixed for years. They've released a bunch of different browser versions and can't make any of them current and stable.

Are you not planning on updating your Chromium version, or have you forgotten how? The Dev version is running on the rotten 140 engine.

The interface twitches when I type an address in the command line. It's annoying.

The interface twitches when I type an address in the command line. It's annoying.

This is already the level of amateur developers who are not able to keep the browser up to date. Soon the release of 139 Chrome, and the version of Chromium on the developer channel is older than on the stable channel and has not been updated for more than a month and a half. If this is how you create the appearance of supporting Manifest 2, then this is a pitiful sight. Why then is there still a warning that your browser will also soon stop supporting the extensions of the second manifest? It would be possible to understand that you are seriously fixing something in the engine, but it seems that you are trying to delay the end of support, and are not doing serious work with the engine so that it supports Manifest 2, you do not have the resources for this. So far, disrespect for users is visible. They do not even backport critical holes, i.e. browser security is no longer a priority. I am waiting for the next scripted phrase of the bot: "We are thoroughly testing to improve the user experience"

Flow stopped working. Resetting and rebooting do not help. Through opera.com/connect it also constantly hangs and there is no barcode.

@andrew84: It's a mess because the company doesn't have a strategy, they don't know who they're making the browser for and why. They have underdeveloped games in the form of Crypto, GX, Air, Neon, and apparently there is no limit to this idiocy, as a result, bugs on a normal browser are not fixed, and they even have a leaky 135 on their Dev channel, when 138 is already stable for other developers.