Opera 12.17 out

Hi all users of Opera 12,

Though I have been a long time in Opera, this is my first blog post for the Desktop team. I normally blog over at the security blog, but since this Opera update is purely about deep security layers, I figure it is time to try something new :)

weatherBut before I can tell you about the security fixes, there is the mandatory weather update. Since a picture says more than a thousand words, here is one with today’s view from the Desktop wing (note the guy sunbathing in the middle).

As discussed in our blog post about Heartbleed, the standalone autoupdater for Opera 12 on Windows was vulnerable to a Heartbleed attack from someone who would be in possession of a valid Opera certificate. While fixing this, we also found another issue with our autoupdate on Windows which might be exploited by someone in possession of such a certificate. Successful exploitation, which would require using a third, unrelated bug on Windows, could allow a mischievous man in the middle to run arbitrary code on the computer. Opera 12.17 is therefore a recommended security upgrade on Windows. While it is unlikely that someone has gained access to a certificate of ours, we cannot rule out that some foreign intelligence agency has done so, and we want to be on the safe side.

Opera 12 for Windows will update itself automatically. Mac and Linux are not affected, and will not receive a 12.17 update.

The discussion area below is to be used exclusively for positive comments, praising our good work :D Transgressors may be ignored, at their own peril.

Opera Next update – 21.0.1432.39


We’re updating Opera Next to 21.0.1432.39. Inside you can find few bugfixes.

Opera will now scale with screens that use 200% DPI setting in Windows. You can check full list of fixes in the changelog.

Be sure to try it out and share your thoughts with us.


  • Opera will scale with 200% DPI screens


Full changelog

Opera Developer 22.0.1460.0, now easier to update than ever

There comes the first Opera 22 update that will benefit from the new silent update process on windows. You should be upgraded to it automatically, without even a UAC prompt.

In addition, to make the autoupdating even smoother, the autoupdate packages will now be sent to you in the form of a patch instead of a full package, whenever possible. This will hopefully help those of you who pay per Mb downloaded or those who have a strict monthly download quota,

In addition to this, this build also contain a few bug fixes and crash fixes. See the changelog for the full list.

For those of you who are curious or need more information in order to produce a better bug report, here are some more technical details:

The silent autoupdate feature is implemented using a scheduled task. Those of you familiar with the Windows Task Scheduler should be able to use it to retrieve information about the task. The scheduled task is supposed to run on system startup and every day initially, but we can adjust it run every few days instead if we need to reduce the load on our servers. When Opera is running, it will keep track of whether the scheduled task is running normally and will attempt to run it manually when needed. If all else fails (which should really not happen), Opera will fall back to running autoupdate itself and in such a case, UAC prompts might appear anyway.

One important exception to silent autoupdate happens if you have installed Opera from a standard user account and elected to install for the “Current User” to a folder requiring administrative privileges. The installer will allow you to proceed as usual, but it will not create a scheduled task. For installations made in this fashion, autoupdate will keep working as it used to instead and UAC prompts might appear. This is obviously because creating a scheduled task allowing silent installation from the standard user account would be impossible.

The patch packages also have their own interesting story. They are generated using bsdiff between a pair of full package. Since we release quite a large number of packages, we can’t realistically create patch packages for every single pair of packages we release (the time required and the amount of storage needed would be prohibitive). Therefore, we only generate patch packages from those pairs which we consider likely to be used as an upgrade path. In other words, if we think many user will upgrade from version X to version Y, there will be a patch package for it. And if we think it is unlikely that people will upgrade from version X to version Z, people using version X will be served a full version Z package when autoupdating.

The process of applying the binary diffs from the patch package is quite simple: First, your opera installation will be copied entirely to a temporary folder, then bspatch will be used to apply the diffs. If applying the diffs fails (and this should really not happen), then a full package will be downloaded and used instead. Finally, when the patch has been applied, the installer is run from the patched opera folder, as if it had been run from a full package, and upgrades the actual opera installation.

That’s all the technical infos for today. Stay tuned for future info about opera in general and autoupdate/the windows installer in particular. As usual, any feedback or bug report is greatly appreciated.

Known issues

  • opera:extensions and opera:plugins are blank
  • opera://about/thanks is shown as plain text
  • [OS X] Crashes when clicking Reload in toolbars asking users to reload to recover from a crash


Opera Developer 22!

Today marks the first release of Opera Developer 22. For this initial developer release our primary focus has been on backend changes to ready ourselves for future improvements in the UI and elsewhere.

Nonetheless, 22 is a major update and includes hundreds of bug fixes, crash fixes and site rendering improvements (see our changelog for the full list).

In addition some UI improvements are already visible, such as a new Encoding Menu, an update to our default themes and a better (silent) update process on Windows. Our new silent update allows for a more seamless update to the latest version. There are no buttons to click and no UAC (User Account Control) dialog interrupting your workflow. You will be automatically updated to ensure you always have the most recent and most secure Opera version.

Note: This build will not silently update, that will happen from the next Developer release.

Thanks again for your testing and feedback, which is (as always) greatly appreciated!


  • Update to Chromium 35.0.1883.0
  • Silent update
  • New default themes
  • Encoding menu


Full changelog

Opera 21 Next includes an option to show the full address

Opera 21 moves from the Developer stream to the Next stream.

Most of the changes are under the hood. Opera 21 supports Aura, a hardware-accelerated rendering of the browser. This enables less-taxing user-interface animations and a sleeker, more responsive feel to the whole UI. It also gives us a solid foundation on which to make future UI changes.

Aura is a big change, but we’ve also included a small change that will please many of you. There’s now a setting to make Opera always show the absolute address, the full URL, in the address field.

While many of you appreciate our emphasis on the domain name and our decision to display only the essential information, our power users and web developers often need to see the full URL. Now, they can. Simply enable the advanced settings and select show full URL in combined search and address bar under Opera’s user interface options. It’s “Hello, absolute address!” from then on.

As usual, we’re hugely grateful for your bug reports and comments. Thank you.


Full changelog

Opera Developer 21.0.1432.24

Are you ready for testing the first Opera Developer release of Spring 2014?

We have a couple of crashes and bugs fixed for you today. The release also includes Chromium update version 34.0.1847.76.

You can check full list of fixes in the changelog.

Give it a try and give us a poke by commenting or reporting bugs  :)


  • Chromium Update 34.0.1847.76
  • Dragging speed dial items onto bookmark bar moves one of them to a speed dial folder
  • Sliding toolbars disappear when switching tabs

Known issues

  • [Mac] Bookmarks bar titles truncated


Full changelog

Opera 20.0.1387.77 update

It’s been a while since I posted here, heh?

Spring is coming at an impressive pace in Europe: last year we still had snow in April, but this year we probably would be able to start the swimming season in less than three weeks.

But enough of swimming plans. Here’s something more important we’re keeping pace with – our release cycle. Today we’re updating Opera Stable stream.

This updated version includes stability fixes and a Chromium update to 33.0.1750.149.
You can read more about the update on our Security blog

Happy surfing!

Download Opera

Full changelog