defaults write com.operasoftware.Opera OPDisableAutoUpdate true
This should be what you're looking for :). If it worked, Opera will tell you "Update checker is disabled" when you go to Opera -> About Opera.
Do more on the web, with a fast and secure browser!
Download Opera browser with:
@mrmatteastwood Install http://launchpadlibrarian.net/345863538/chromium-codecs-ffmpeg-extra_62.0.3202.94-0ubuntu0.16.04.1317_amd64.deb (you can upgrade it again to the most recent version once Opera 51 stable has been released).
The problem is that Chromium was updated to 64, and the chromium-codecs-ffmpeg-extra package that comes with Chromium 64 only works with Opera >=51.
The other way around as well: Opera 51 will only work with chromium-codecs-ffmpeg-extra >=64, so once Opera 51 has been released and you've updated, you'll have to upgrade this package again.
Hi @jc1742, the removal of the text encoding menu follows a similar move by the core of Chrome, on which Opera is based. You can read more about the decision and its effects in Google's bug tracker here: https://bugs.chromium.org/p/chromium/issues/detail?id=597488 .
I don't see any extensions in Opera's collection right now that would allow you to change it, but there's an extension to install Chrome extensions here: https://addons.opera.com/en-gb/extensions/details/download-chrome-extension-9/?display=en
After installing that you should be able to use: https://chrome.google.com/webstore/detail/set-character-encoding/bpojelgakakmcfmjfilgdlmhefphglae?hl=en which is an extension allowing you to change text encoding.
Thanks both, we're looking into this.
You haven't been hacked @markdavisart - but Google (more specifically, Google's sites) have a heuristic that tries to determine which country you're really from. Since you're using Opera's VPN, and many people from Russian-speaking countries are too, it smartly determined that you must be Russian-speaking!
Not much to do about this apart from changing the language in your Google preferences. And maybe hoping that their algorithm will become a bit smarter still.
You can also set the environment variable
OPERA_AUTOUPDATE_DISABLED. This works on all platforms.
For Opera 32 and newer, you can use a global Apple preference. From Terminal, enter one of these commands:
defaults write com.operasoftware.Opera OPDisableAutoUpdate true
defaults write com.operasoftware.OperaNext OPDisableAutoUpdate true
defaults write com.operasoftware.OperaDeveloper OPDisableAutoUpdate true
Hi @bleduc1 , this was due to a very bad crash bug that was fixed in version 51.0.2830.62. Due to unrelated concerns we weren't automatically updating users to newer versions in the last two weeks which meant that you might not have received the fix automatically. You should be updated to a newer version now.
Hi @sjmgarnier , make sure you install Flash via https://get.adobe.com/flashplayer accessed from Opera. There are different editions of Flash, and the one that works with Safari and Firefox doesn't work with Opera, whereas Chrome comes with an integrated version of Flash.
Seems to be because the site has multiple frames that are independently scrollable (top header, news categories on the left, news articles on the right). Scroll-to-top only scrolls the main frame to the top, which is not scrollable in this case so nothing happens.
I'm not sure if Opera should try scrolling up all frames on the site or we should just accept that it doesn't really make sense on multiple-frame sites.
@thunderclutch I believe this is related to allowing Opera to handle mailto: links on for example gmail. i think there's something wrong here but I'm not yet sure what exactly
But just for clarity for others passing by: you do not need an extension to share links via mail in Opera on Mac, you can use the Share menu for this which is a system facility.
@fjuk We don't 'choose' to limit this functionality. Unfortunately there are complicated legal restrictions around distributing support for H264 video decoding, and it comes down to 'we can't give you this functionality ourselves'.
Therefore we rely on others to give it to you. On Windows and Mac, it's the operating system that provides libraries that do H264 decoding, and Opera uses those. On Linux it's a bit more complicated, but it comes down to 'we use what Chromium uses except we can't give it to you ourselves'.
Unfortunately this means that now and then, when the library Chromium uses changes, Opera needs a certain minimum version of the library to be able to work with it. The rule of thumb is that Opera can always use a library if it's the same version as the Chromium version Opera is based on (check opera://about to see which Chromium it's based on), and sometimes older versions, depending on when Chromium last changed the library. Since the library changed in Chromium 67 / Opera 54, we currently can't use older ones.
While we are waiting for the stable package to be updated in Ubuntu's repositories, if you want a more official, Ubuntu-supplied up-to-date version of the codecs package, there's a package available for Cosmic Beaver which is already at Chromium 67. You can find it here: https://packages.ubuntu.com/cosmic/chromium-codecs-ffmpeg-extra .
Both history (sites you've visited) and typed addresses (things you've typed into the address bar) are removed when you click Opera -> Clear Browsing Data... and select an appropriate time range at the top (by default it removes accesses from the last hour).
If you have visited a site, it would appear that Opera remembers it in terms of the autocomplete function. Even uninstalling and reinstalling from scratch doesn't make it forget.
As with other applications on Mac, Opera has a profile directory, which doesn't get removed when you remove the application itself. You can find it in $HOME/Library/Application Support/com.operasoftware.Opera, and you're free to remove it. This will remove all data that Opera has saved.
And if you want to remember later where to find it, the directory is also listed in Opera's about screen, which you can access using Opera -> About Opera.
Everyone, my most sincere apologies, I read some information wrong: the fix for the remaining issue that occurs after opening a new window was not backported to O58 in time for the initial release, so it'll only be in the next O58 update to come along. This will be released at the start of next week.