Opera 125 Stable

[aswinsanthosh]

aswinsanthosh last edited by

opera on Linux under wayland session runs as unknown app, no icon(show default app icon from system), Therefore it runs as different from pinned icon if that make sense. From what i understand Opera do not provide an application ID, thereby this behavior. it isn't a new bug it existed for years i think, whenever we run opera by setting ozone platform to auto or wayland this used to happen. Now Opera deaults to Wayland its great that it does, Major distros have move to wayland by default. I think its time opera to fix this aged bug

[aswinsanthosh]

aswinsanthosh @aswinsanthosh last edited by

@aswinsanthosh: There is also a bug, Opera crashes if set Sidebar to autohide.

kindly address these two issues.

Opera running as Unknown App.
Crash on setting sidebar to Autohide

both on opera running in native wayland

i know the workaround is to set ozone platform to X11, but i think its time to fix it for native wayland

[ironbone]

ironbone last edited by

The opera menu is still too small
https://ibb.co/pj6VkZ3t
I use Ubuntu + Gnome - the newest versions

[ironbone]

ironbone last edited by

The pop windows with videos (for example YouTube) still do not work well. The position is on the left top of the display. Additionally, they do not stay in foreground

[ironbone]

ironbone @ironbone last edited by

@ironbone:
This is connected with Wayland. On X11 it works well

[ironbone]

ironbone @ironbone last edited by

@ironbone:
This is connected with Wayland. On X11 it works well

[rick2]

rick2 @Opera-QA-Team last edited by

@Opera-QA-Team
Hello,
The new update 125.0.5729.15 is still broken on Linux under Wayland, it crahses and won't open.

$ kinfo
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.10-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics

[zibi1981]

zibi1981 @rick2 last edited by

Opera still crashes on my CachyOS with KDE. Here is a portion of the error code (forum rules won't let me post whole)

opera
[1206/095137.272067:ERROR:third_party/crashpad/crashpad/util/file/directory_reader_posix.cc:43] opendir /home/cardiozibi/.config/opera/Crash Reports/attachments/ae163632-27b2-43cf-8fe7-053fe6f2814f: No such file or directory (2)
[7503:7503:1206/095137.702299:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7503:7503:1206/095137.702402:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7503:7503:1206/095137.702417:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7503:7503:1206/095137.702438:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7503:7503:1206/095137.755955:ERROR:cc/paint/skottie_wrapper_impl.cc:46] [Skottie] "Failed to parse JSON input.
"
(...)
[7686:7686:1206/095138.461044:ERROR:chrome/browser/process_singleton_posix.cc:231] read() failed: Połączenie zerwane przez drugą stronę (104)
fish: Job 1, 'opera' terminated by signal SIGSEGV (Address boundary error)

~
❯ [7686:7686:1206/095138.727061:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7686:7686:1206/095138.727125:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7686:7686:1206/095138.727134:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7686:7686:1206/095138.727146:ERROR:extensions/common/url_pattern_set.cc:298] Invalid url pattern: chrome://startpage/*
[7686:7686:1206/095138.780731:ERROR:cc/paint/skottie_wrapper_impl.cc:46] [Skottie] "Failed to parse JSON input.
"

[sgrandin]

sgrandin @Opera-QA-Team last edited by

@Opera-QA-Team Website fixed it

[filbo]

filbo @Opera-QA-Team last edited by

@opera-qa-team: I understand what you're saying, but it is self-inconsistent (there was a release in between those two, which mentioned only two bugs). And it is negative to the viewer of the changelogs. I checked the similarity because as I was scanning the newer list, it seemed hauntingly familiar.

If you didn't expect anyone to look at the changelogs, there is no point in posting them. On the other hand, if you do expect people to look at them, please curate them so that they present only new, useful information. It is ok (i.e.: highly encouraged) to say something like 'this release includes all of the fixes mentioned in the changelog for prior release (123.456.whatev)'.