Opera 126.0.5742.0 developer update
-
Opera Comments Bot last edited by
Hello! New update to Opera developer is here (version: 126.0.5742.0)! Key highlights: For a full list of changes check out our changelog. Happy browsing! Installation links:
Read full blog post: Opera 126.0.5742.0 developer update
-
andrew84 last edited by
there's still bug (in Stable also) for the EasySetup when dragging the scroll bar.
https://forums.opera.com/post/394135 -
KenedSF last edited by
In Linux (Ubuntu and Zorin OS), the picture-in-picture video window does not overlap other windows. They do not overlap. This applies to the stable, beta, and development versions of Opera.
-
KenedSF last edited by
Suggestion: the Mirage theme could allow changing the wallpaper. For me, this is the best theme, but I would like to be able to change the wallpaper.
-
andrew84 last edited by andrew84
The bar at the speed dial page's bottom is still not fixed (the bug reached Stable).
And while starting the browser the bar is red and I'm not alone who sees this > https://forums.opera.com/post/396831*additionally I see the full screen red flash when restoring minimized window.
-
Opera-QA-Team Opera last edited by
@andrew84 Thanks for pointing this out, we'll take a closer look!
-
Opera-QA-Team Opera last edited by
@andrew84: Hi, thanks for reminding. We are checking this. The problem is, it doesn't happen for everyone so we need to find the common point as we weren't able to reproduce it.
-
Opera-QA-Team Opera last edited by
@krteq Hi please take a look at our latest stable release - we made sure opera for KDE is working correctly :))
-
tastodd last edited by
@andrew84 said in Opera 126.0.5742.0 developer update:
The bar at the speed dial page's bottom is still not fixed (the bug reached Stable).
And while starting the browser the bar is red and I'm not alone who sees this > https://forums.opera.com/post/396831*additionally I see the full screen red flash when restoring minimized window.
Maybe it's related to the graphics adapter and driver?
I'm running Windows 11 25H2 (100% scaling) with an Intel 14600K processor and integrated Intel(R) UHD Graphics 770 without any issues. -
andrew84 last edited by andrew84
@tastodd said in Opera 126.0.5742.0 developer update:
Maybe it's related to the graphics adapter and driver?
I don't know.
But according to the posts (including reddit) it's rather OS dependent, seems like win 10 is affected. -
Opera-QA-Team Opera last edited by
@rancor6: Hi, we know the issue, it refers to Win10 only. The bug is awaiting fix.
-
filbo last edited by
Two issues, probably not version-specific, but here we go...
TLDR: (1) 'singleton' intended to keep multiple Opera processes from co-running not working; (2) tons of defunct
opera-autoupdatprocesses.First issue:
(1) my currently running opera-developer is (was) 125.0.5720.0
(2) I allowed the system (Debian 'sid') to update opera-developer several times without actually restarting the process (so 125.0.5720.0 is still running, but something else is in the filesystem; a frequently-changing 'something else' as you issue more updates
(3) today I right-clicked on a URL in my terminal (actually the changelog for 126.0.5744.0, which is queued to be updated) -> Open -- this caused opera-developer 126.0.5742.0, the currently installed-on-filesystem version, to start a new window containing the same tabs as the currently (and still) open 125.0.5720.0 process.
(4) on examination, ~/.config/opera-developer/Singleton* exist and are dated ~10 minutes ago, i.e. when the 126.0.5742.0 process started. The 5742.0 process has SingletonSocket open for listening.
(5) two different directories exist in /tmp, with different SingletonSockets, each of which is open by one of the processes; but the symlink from ~/.config/opera-developer has been changed. I don't see how 'singletons' are 'single' when they rely on a replacable symlink which the program replaces automatically!Second issue: there are some 600+ defunct 'opera-autoupdat' processes, children of the 125.0.5720.0 process; it seems to have started about 100/day on Dec 5-6-7-8-9-10 (starting with 5 on Dec 4). These might have started when 126.0.5734.0 was installed in place of 125.0.5727.1 (Dec 4 19:44). Unfortunately
psdoesn't show exact start times of defunct processes from days ago.In any case, the parent process of
opera-autoupdatshould be wait()ing those processes! -
filbo last edited by
After posting that, I tried to get out of the situation. First I made a backup of ~/.config/opera-developer; then I closed the 126.0.5742.0 window. At that point the 125.0.5720.0 window went crazy, suddenly replacing every tab with a bunco of old Facebook tabs.
So I closed the 125.0.5720.0 window. Once I was sure no Opera processes were running, I completed the update to 126.0.5744.0, then started it, and of course it was a bunch of old Facebook tabs. Specifically, 14 of them, plus an 'Opera has been updated' tab. But when I tell it to close the window, it prompts me that 26 tabs are being closed(?!?).
Closed it. Moved aside ~/.config/opera-developer, replaced it with the backed-up copy. Started 126.0.5744.0 -- and it has my expected current set of tabs.
So, something very wrong with the singleton stuff; and, probably expected shenanigans when unintentionally running 2x simultaneous Opera processes out of the same config directory. Except the '15 tabs = 26' thing is weird.