Posts made by ruario

http://ruario.ghost.io/2014/12/23/installing-12-16-alongside-modern-opera

No that sounds perfectly fine. You didn't have the dependencies -f install fixed it. There is no issue here.

I'm bored! Here is a script that automates building the required libs.

Note: You will still need to install a suitable build environment first, containing: autoconf, automake, gcc, gcc-c++, libtool, make, nasm, pkg-config and the zlib development support files.

All paths in my post above that refer to /usr/lib64/opera-developer, should actually state /usr/lib/x86_64-linux-gnu/opera. If a moderator drops by and wants to edit and fix my posting, so much the better. In the mean time I have updated the blog post.

I have updated my blog post.

They use Openh264.

Using the host OS to decode—for Linux that would be system FFmpeg libs—was considered to produce the best solution for the majority of Opera's desktop users, with the least effort. You should also keep in mind that all solutions are a compromise of some kind.

Switching now to Openh264 would not be a simple undertaking and current solution does work well for many. For those of you encountering problems on Linux, I posted a work around above.

@gustavwiz don't worry I never really moderated anyway. @avl and I discussed this already and if I really wanted mod access I am pretty sure it would be given to me but I don't need it.

Umm, thanks @avl. I see you guys also removed my moderation rights. Oh well, fair enough I suppose!

Well the only person I knew working on the forums, has also left. Not sure who has taken over. So not sure who to ask about removing my badge.

ruario, all the very best to you. If you end up over at Vivaldi, or Maxthon, I'll be sure to give their browsers a try again. I feel more comfortable using a browser that I know you're standing behind.

Follow me on twitter and you will find out what I do in the future.

Is there any chance to make next betas to be compatible with ffmpeg 2.4.3 or when do you plan to release stable (which I hope will remain to be compatible with 2.4.3) with sidebar support ?

This could also be a good work-around…

Not really, as it is non-trivial to do and hence very unlikely (IMHO).

Okay. Anyway, the user shouldn't have to mess around with this. It would be much better if Opera included the right version of ffmpeg.

Opera installs the right version of FFmpeg. They just don't include one with built-in h.264 support due to licensing issues. H.264 is patent encumbered and not cheap. Before anyone goes and suggests Opera should just buy a license, I am fairly certain that would not be financially viable. Hence we have this non-optimal situation.

If people are continuing to have problems, just build the correct version for yourself—this is the most reliable way to ensure you have a suitable version. It is not as hard or as scary as some people might think!

First install a build environment:

sudo apt-get install automake build-essential libtool pkg-config yasm zlib1g-dev 

(For non-Debian dirstos you want to install the following packages: autoconf, automake, gcc, gcc-c++, libtool, make, nasm, pkg-config and the zlib development support files)

Fetch the source code for the version you want to install:

wget http://ffmpeg.org/releases/ffmpeg-2.6.3.tar.bz2

Extract the source code:

tar xf ffmpeg-2.6.3.tar.bz2

Build an ffmpeg suitable for Opera:

cd ffmpeg-2.6.3
./configure --build-suffix='-opera' --enable-shared --disable-programs --disable-doc --disable-debug --disable-encoders --prefix=`pwd`/staging
make install

Install the libs into Opera developer (adjust the path as needed for stable or beta):

cd staging
find lib -name '*.so*' | sudo cpio -pvd /usr/lib64/opera-developer

(You will need to restart Opera before the new libs are detected)

You can also make a backup of these binary libs to allow you to install on your other machines:

find lib -name '*.so*' | tar fvacJ ffmpeg-2.6.3-binaries.tar.xz -T-

To install from the backup archive:

sudo tar xf ffmpeg-2.6.3-binaries.tar.xz -C /usr/lib64/opera-developer

Cannot remember where I got it, but whoever did it really helped me out.

I can make a guess, read the post that is 6 above yours!

Wine? What the hell? Why?
http://ruario.ghost.io/2014/12/23/installing-12-16-alongside-modern-opera/

Opera stable is not yet available for 32-bit, so no it won't work—it will if Opera releases a stable 32-bit Linux release.

I also think you are making it overly complex. Install the .deb and the repository is setup for you. If you must setup the repository manually first for reasons I cannot guess, read http://deb.opera.com/manual.html.

P.S. I no longer work for Opera

…the Oslo desktop team was shut down—Opera desktop development continues in Poland (along with 3 people in Nice). The vast majority of the Oslo desktop team were not offered new positions in other divisions, but a handful were. However, as I did not want to work on a non-desktop product and due to the fact that many of my closest friends lost their jobs entirely, I decided to quit. The company no longer has the same spirit that it did when I joined—at least from my personal perspective—so I felt it was time for me to go. Nonetheless, there are still many people working in Opera whom I care for deeply, including many of those who remain in the desktop team and I so wish them the best of luck.

as several that worked with the desktop browser have been dismissed, including Ruario, I don't think it will come in the near future at least.

For the record I was not dismissed. What actually happened was that the Oslo desktop team was shut down—Opera desktop development continues in Poland (along with 3 people in Nice). The vast majority of the Oslo desktop team were not offered new positions in other divisions, but a handful were. However, as I did not want to work on a non-desktop product and due to the fact that many of my closest friends lost their jobs entirely, I decided to quit. The company no longer has the same spirit that it did when I joined—at least from my personal perspective—so I felt it was time for me to go. Nonetheless, there are still many people working in Opera whom I care for deeply, including many of those who remain in the desktop team and I so wish them the best of luck.

With regards to the original question, I have been negligent in updating my repository after leaving Opera. It is a personal and somewhat emotional thing. As much as I like the team, I have struggled to care about the future of the product after everything that has happened—this is not to say that they don't care about it, so I am not suggesting that "the end is nigh".

That all said, I previously published example Opera .spec files on Github, so anyone is free to create a new repository. It is really not that hard. Well within the scope of a moderately experienced Linux user. The Open SUSE Build service is free to use and makes maintenance a breeze, with the tools and automation provided.

In the mean time, one could also use my rpm4opera script to quickly generate rpms from the debs that Opera provides.

I am no longer en employee but I just wanted to drop by and say that yes, employees do read this forum.

The key point is

You are adequately sandboxed.

SUID sandbox is not needed if your kernel supports the other required features (kernels of 3.17 or newer almost always will and some older kernels if they have been suitably patched by your distro).

P.S. The sandbox is still SUID in post install of packaging because not everyone has a suitable kernel.

P.P.S. It seems that I still have an employee badge but I have left Opera now, following the shut down of the Desktop team in Olso.

`

Look this mustn't have been a small/rushed decision, if a plan had changed we'd have seen consequences already like features in development being dropped so that they can work with less resources or something like that. That didn't happen, we saw configurable keyboard shortcuts rising in the beta versions of the browser, new mouse gestures, even a Linux 32-bit version that I personally consider almost useless, etc.

With regards to time scales, changes can happen very quickly!

I was given quite a lot of autonomy with regards to Linux and hence it was ultimately my call to put the 32-bit builds out. I chose to do his despite the fact that the figures we have from 12.16 would suggest that almost nobody would use 32-bit Linux builds.

I was the Linux team lead but also the primary tester. So I figured that I would shoulder the burden of extra testing. I wanted to put the builds out as I cared about the users left behind.

However, had I known this would happen—and I didn't have the vaguest idea—I would not have put out 32-bit Linux builds. I care about the remaining Linux guys in the Opera desktop team and would not have have wished to increase their workload at a time when—due to the losses—they will already have too much work on their hands.

All bets are now off with regards to if 32-bit Linux Opera builds will remain. Part of me would hope that they do but in reality if I could advise the team, I would suggest they try and back out of going to stable with 32-bit. The resources will be needed elsewhere. I'm now pleased I said, "I am not going to promise that we won’t drop 32-bit again.". Perhaps it gives them some wiggle room.

The 70 employees around the world that are leaving the company aren't all from the desktop browser development team.

True but a large percentage of them are. All that said, I wouldn't write off the remaining team quite yet. They are a smart and hard working bunch. If anyone can pull together and keep things running, it is these guys. Not only that, I consider them all friends, so I can only wish them well!

@blackbird71 If you want more thoughts read Daniel's blog post—I'm still trying to decide if I will write anything myself.

P.S. There was also coverage in the Norwegian media, e.g. http://www.dn.no/nyheter/finans/2015/04/20/2040/Opera-Software/opera-software-kutter-70-jobber (Google translate doesn't totally butcher it, if you can't read Norwegian)

The Linux Chromium-based browsers have not supported NPAPI plugins for far longer than their Mac and Windows cousins. Support for NPAPI will never be added. So unless Oracle finds some way to provide a PPAPI plugin you will not get Java working.