I don't know exactly, I guess it's one of them: (network part) --disable-ipv6 --disable-captive-portal-bypass-proxy --ssl-version-min=tls1.2 --cipher-suite-blacklist=0x000a,0x0004,0x0005,0x002f,0x009c,0x009d,0x0035,0xc011,0xc007 --no--pings --disable-background-networking --disable-extensions-http-throttling --disable-client-side-phishing-detection --disable-cloud-import --disable-component-cloud-policy --disable-datasaver-prompt --disable-gaia-services --disable-ntp-most-likely-favicons-from-server --disable-ntp-popular-sites --disable-system-timezone-automatic-detection --disable-offer-upload-credit-cards --disable-credit-card-scan --disable-wake-on-wifi --disable-cast-streaming-hw-encoding --disable-web-resources --disable-web-sockets

EDIT: nvm, I guess this was just a fluke on a coincidental day I happened to be observing what happened when you stayed on the page while disconnecting. after 2 days now I can verify it hasn't happened again. I am interested to know what may have caused it to clear though >.>

@jimunderscorep ...yes

@jimunderscorep See, that's where the difference lies: I can do that as a user, no problem, because I edit my own profile. Installed programs, or program folders, for this I need root rights. Open the console, type Pw, then do the required action. Mostly I work with zypper

@unknown-user01 said in Command-line-switch to enable vpn?: I searched for the command switches via startpage.com and tried them around. I found some of them here: https://peter.sh/experiments/chromium-command-line-switches/ Hey, I have that page of chromium switches bookmarked too! Vpn on the other hand, is an opera-specific function and, since it is not listed in the extra switches of opera --help, it probably does not have a switch.

Are you on regular opera or snap? Also, may I ask what version of chromium does ubuntu have right now in its repos? I assume it is 75.x, which is still compatible with chromium-75-based opera 62. Keep in mind though that chromium 76 was released a couple of days ago, so things will break again once ubuntu packages it.

Udemy needs an account to let you access these videos, so I can not find what codec it uses, but it will be h264 most likely. If that is the case, make sure you have libopenh264 installed, plus all 3 libav* ffmpeg libraries. That is for ff (and chromium, in case you also use it), opera will not use them at all, although it could and it should.

Kali logs you in as root, because many of its tools need root priviledges to run, and opera, being a chromium-based browser, can not be run as root. https://crbug.com/638180 If you do want to run it, regardless of any issues you may encounter (scurity or stability ones), edit its shortcut so as to make it launch with the --no-sandbox parameter.

No problem here, with ff 68.0.1 on debian, as seen on the image. It just downloads the deb file as it is supposed to Are you using some firefox extension that changes the user agent?

Observation regarding repositories is no more relevant here. It belongs to Red Hat Bugzilla – Bug 1733949.

@adasiko said in Your file was not found, if the file resides in /tmp: @jimunderscorep said in Your file was not found, if the file resides in /tmp: removing the snap version of opera and installing the deb one. And welcome to "Some videos not playing?" club. Well, if someone has opera installed as a snap, he has probably installed it from ubuntu's "store" (I can't remember its name), so he is already using ubuntu or a derivative. It is really very to be using snap in debian or fedora or arch etc, because snap is not forced on users of other distros. So, since he is already on ubuntu, he can install install opera as deb and chromium ffmpeg codecs, have the same result and benefit from the advantages of a real app over a snap one (lack of useless/pointless permissions, less space on disk, proper theming, access to system wide configurations for mail://, magnet://, etc). I know you will say "but chromium ffmpeg codecs and opera versions do not match sometimes". For that, feel free to blame the ubuntu and/or the opera devs respectively, depending on which is left behind each time.

@somegeiser said in Get "Access Denied" going to some websites - Like Home Depot: Access Denied You don't have permission to access "http://www.homedepot.com/b/Outdoors-Outdoor-Cooking-Grill-Replacement-Parts-Grill-Grates/N-5yc1vZbxde" on this server. Reference #18.20a9645f.1564065244.47ff7a7 Why is this happening? Is it because I am using VPN? I got an 'access denied' message with vpn enabled only if the location was set to Europe -- this is probably an issue with the GDPR (or just a server misconfiguration). (it works fine if the location is set to something other than Europe)

Thank You. Reinstall from web w deb one fixed the problem. You have made my day.

@neoh4x0r said in Videos in HTML5 will not work: A second, but more complicated option, is to directly build libffmpeg from the chromium-browser source -- which is exactly what every packager of chromium-codecs-ffmpeg-extra does. (the latter is what I do -- compile from source; only because I was having issues finding the extract version of chromium-codecs-ffmpeg-extra (depending on the version I might find it or not). Like I was saying compiling libffmpeg is not easily done as it requires checking out the entire code-based for chromium browser and then checking out the specific revision -- tied to the tagged version that is needed. Also even before checkout, there is a complicated dance needed to be done to run the depot_tools gclient (which is a custom client used to stage and build the source). Yes, telling people just to use a different browser is an option, but for people who are largely tied to the browser that they use....that isn't really an actual option for them. And, so since opera does not ship a proper libffmpeg.so (it is built based on chromium, the target can be changed to a chrome build). The chromium target lacks support for certain codec, but chaning the target to chrome exposes all of the extra codecs (changing the target is as simple as editing a single file and replacing a string). in third_party/ffmpeg/ffmpeg_options.gni : change ffmpeg_branding = _default_ffmpeg_branding to ffmpeg_branding = "Chrome" It means that every user who is not running Ubuntu will have to resort to some out-of-band/out-of-channel process or procedure to get proper libffmpeg support in opera (meaning taking pre-build packages and extacting the plugin, or building from source, etc -- it just the way things are. The might even be Google trying to force people to use chrome -- since the only official build that supports the codec is a "chrome" branded build.

@jimunderscorep Ok, I understand. Sorry. For those who use Debian or Ubuntu, try this package: chromium-codecs-ffmpeg-extra_75.0.3770.90-0ubuntu0.19.04.1_amd64.deb I'm not sure if package installation will help, but the library from the package will. The DEB , RPM , xz packages can be opened e.g. by Ark or others unzippers. Other working example for Arch users: opera-ffmpeg-codecs-75.0.3770.100-1-x86_64.pkg.tar.xz A libffmpeg.so file from both packages works also in Fedora 30. To install codecs in a proper way for a particular distribution there must be a good guy who will pack it. Today I only know a workaround - copy library from package to the system library directory.

Asking for a friend: what is the name of the browser?