Aria 2.1 (Opera One version: 104.0.4944.33) is still unstable.

I cannot give instructions on how to reproduce that because it seems to happen randomly. But when it happens, it seems to happen when Aria is sending an answer. Halfway the answer, Aria closes and cannot be restarted without restarting the browser. When I restart the browser en continue to work with Aria, it says the answer was interrupted. When I click the Retry button, the answer is displayed without problem and Aria is working OK until it crashes again.

Still not fixed in version 103.0.4928.34.

BTW, when I right-click a bookmark on the bookmarks bar and choose Edit, I get an even worse result:

As with the address bar, this has been the case for a long time.

Still a white address bar in private mode in dark mode.

@donnerwetter said in General Aria Feedback Topic:

Til friday Aria worked fine on each device, now "she's" dead.

Confirmed.

I successfully uninstalled Opera Browser Assistant and it remained uninstalled after my last Opera update from within Opera itself.

Here I will share information about it, so others may benefit from it.

Uninstalling Opera while keeping your personal data and installing Opera again using the Offline Opera Installer no longer works te remove Opera Browser Assistant.
Apparently the installer now detects you had Opera Browser Assistant installed and installs it again.

Here is how I removed Opera Browser Assistant:

• Uninstall Opera without deleting your personal user data.
• Download and run the Offline Opera Installer.
• Do not start the installation yet, but open Explorer and go to the folder:

%localappdata%\Temp\.opera\Opera Installer Temp

• In this folder go to the folder containing the setup files. The folder is named like this:

opera_package_<timestamp>

• Delete the file named "extra_apps".
  In my case Opera Browser Assistant was the only component listed in this file. You may want to edit this file if you have more components listed in this file.
  Alternatively you can remove the folder "assistant" and leave the "extra_apps" file intact.
• You can now close Explorer and continue with Opera Installer.
• Set your preferred options in the Opera Installer and install Opera.

After this, new Opera versions downloaded by the Opera Update feature, no longer seem to include the Opera Browser Assistant package.

I filed a bug report for this issue, but an irrelevant automatic response was sent and the bug report was closed automatically. Despite what the confirmation email suggests, I am not able to re-open the bug report by adding additional information to the bug report. And I'm not filing the same bug report again.

Preconditions:

• Already have Aria working in Opera

Issue:

• With Opera pinned to the Windows taskbar, directly open Opera in private mode by right-clicking the icon in the taskbar and choose New private window.
• Open the sidebar and click on the Aria icon.
• Click Get Started
• Click Continue to sign into the Opera account
• Sign into the Opera account.
• → Aria is not working and reloading doesn’t solve it.
• Now, press Ctrl+N to open a normal window (not in private mode)
• Click Get Started
• Click Continue to sign into the Opera account
• Sign into the Opera account.
• Now Aria says:
  ”Thanks for signing up!
  There are many others joining right now, so I’ve added you to the waiting list. I'll notify you in the coming days as soon as access is available.”
• The statement by Aria is false and you can use the Reload button at the top of Aria to start using Aria.

@andrew84 said in Difficult in creating a new account:

@whisperer said in Difficult in creating a new account:

you have to click a Login button,

You mean the opera account popup on the address bar?
If yes, I agree. There should be a direct way to login using the popup instead of redirecting to web page. It should redirect only if someone wishes to create new account.

I mean things like these:

If the user wants to create an account, he has to click Login and then there is no hint for creating an account.

@andrearobinson said in Aria's answer in a blockquote not visible:

It looks like the blockquote height is set too low, causing visibility issues. You can resolve this by using the following steps:

• Right-click on the blockquote, select Inspect Element.
• In the CSS panel, find the blockquote element and change the height to auto or remove the height property altogether.
• Refresh to see if the issue is resolved.

It looks like your post is an AI generated spam post. Your text suggests that you haven't tried it yourself and it makes no sense.

It is already determined in this thread that it is not due to the height that nothing is displayed, but that there is no text in the generated HTML. Furthermore, your suggestion makes no sense because doing a refresh negates the changes you made in the Element Inspector.

Still a white address bar in Opera One version 105.0.4970.13.

Other theme issues are fixed, like the "This tab is playing audio" text, the world map of the VPN setting, editing bookmarks by right-clicking bookmarks in the bookmarks bar.

Still not fixed in version 101.0.4843.43.

And here's what you get when clicking the icon:

Apparently, the popup box cannot handle long user names like "Opera Comments Bot".

@leocg said in Opera 120.0.5543.53 beta update:

@whisperer said :

. But I do have trouble with the changelog entry "DNA-123014 Promote 120 to stable" listed for the build 120.0.5543.53 in the full changelog. From the user's perspective that doesn't make sense.

That could be an example of things being complicated unnecessarily.

If the changelog is for the whole main version number, of course it will show information about that version starting on developer channel, being promoted to beta and to stable.

As you yourself said: "You can see what changes were made during beta stage by looking at the build numbers." That's not the case for this changelog entry.

It is, it shows the changes from when version were in developer channel up to more recent ones in stable channel.

I expect moderators to model respectful dialogue, not dismiss users' concerns with vague, accusatory remarks. You are doubling down after being respectfully asked to stick to discussions about Opera.

Furthermore, you are dismissing two specific points I raised with general remarks which are not addressing the raised issues at all. In doing so you are undermining meaningful discussions about Opera.

I consider this trolling behavior, something you have showcased before. Responding to such behavior is not productive, so I will no longer respond to posts by you.

@burnout426 said in Opera 120.0.5543.53 beta update:

Hovering over the "blog post" link for each and looking at the URL will show whether it's a developer, beta or stable build. You can even see if it's the initial developer/beta/stable build for that major version by the lack of "-update" in the URL. Think it would be nice if that info was in the header for each build though in the changelog.

That would indeed improve clarity. Additionally, a link to a page with an explanation of full changelog pages could be helpful too.

@leocg said in Opera 120.0.5543.53 beta update:

@whisperer Everything that is being discussed here about Beta channel have been updated to the same version of stable channel.

It's not something new, Opera has been doing it since a while already and, like I said, started by request of (some) users.

Also, Opera once said that people should follow channels and not version numbers, that only exist to make things easier for people.

That's not an answer to my question. If you are not willing to explain why you think I am unnecessarily trying to complicate things, I respectfully ask you to refrain from posting off-topic thoughts about me and stick to discussions about Opera.

I have no trouble with the existence of beta and stable builds with the same major version number. But I do have trouble with the changelog entry "DNA-123014 Promote 120 to stable" listed for the build 120.0.5543.53 in the full changelog. From the user's perspective that doesn't make sense.

As you yourself said: "You can see what changes were made during beta stage by looking at the build numbers." That's not the case for this changelog entry. The explanation given that the full changelog consists of a combination of indistinguishable beta and a stable changelogs where the beta changelog can contain entries that doesn't apply to the build it is listed under, but to an earlier build, doesn't make it logical and understandable for users.

@leocg said in Opera 120.0.5543.53 beta update:

@whisperer And I think you are trying to complicate things unnecessarily.

Enlighten me, what am I trying to complicate unnecessarily and how am I trying to do that?

@leocg said in Opera 120.0.5543.53 beta update:

@whisperer The changelog is for the whole version.

You can see what changes were made during beta stage by looking at the build numbers.

Exactly my point.

@daria19 said in Opera 120.0.5543.53 beta update:

To add some context: the previous changelog entry for version 120 was about its initial stable release, and the next one referencing 120 was for the beta channel. That beta changelog includes the note that 120 is now available not only in beta but also in stable, which signals the promotion.

There is a beta changelog? Cool. Where is it? I have only seen the full changelog which contains changes of beta and stable versions without distinction.

If you need to repeat a change for an earlier stable version, why not for all the changes of the earlier stable version?

The issue on opera://bookmarks/ still remains, where there is no cursor on the folder that is open when navigating folders at the left using the keyboard (Tab key).

The issue on opera://update/ still remains, where the contours of the "Check for update" is visible when disabled, but invisible when enabled.

Still not fixed:
@whisperer said in Opera 120:

About pressing Ctrl+/ in private mode:

@marinaz909 said in Opera 119.0.5497.56 Stable update:

@whisperer If I understand correctly, you see a darkened screen but no popup informing you that Aria isn’t available in private mode...

@whisperer said in Opera 119.0.5497.56 Stable update:

@marinaz909
I'm using the Windows version. It's because I open directly into private mode by right-clicking the Opera icon in the task bar. It doesn't happen when I first open Opera in normal mode and then open a private mode window. A screenshot will of course not help in this case. You got it right, I just get a darkened screen, nothing more.

Issue not fixed or back again in Opera 120.