@denisftw I have lost count of the number of different solutions that have been put forward for these problems, all involving somehow obtaining a different version of libffmpeg.so which may not work with any other piece of software, and which can not be relied on to work with a particular version of Opera.

We're told it's because of patents, or mismatched library versions, or a library version needed specially for the new version of Opera which hasn't been released yet (and that all seems to miss the whole point of a library).

I am getting confused, and I am beginning to doubt if anyone else really knows a reliable answer. There seems to be too much of "It works for me so it must work for everyone."

I am trying to stay polite, but if "Tee-Emm" were still around and were dealing with computers, an award of The Most Highly Derogatory Order of the Irremovable Finger would already be in the post. Some of you deserve Season Tickets for your local ambulance service. The gabbling puts me in mind of a flock of chickens arguing over which end of the egg to to hatch from.

The most reliable fix seem to be to stop using Opera to read Twitter.

I was having password problems today, one particular password, current Opera version, and the Synchronisation tool fixed it. It's under Settings > Basic. It's useful for keeping stuff matched between different machines, and one reason I keep using Opera despite the problems there can be with video codecs.

I know this is an old thread, but it keeps popping up on search engines. This answer works in August 2018, v55.0 under Linux.

Something started going wrong for me today, similar loss of passwords, but different timing, so I wonder just what exactly is breaking.

An update on this.

v57.0.3098.91 is working OK

As of right now, a new version is available, but I had to back out of the upgrade because of loading problems. Linux, it seems, is such a broad target that, when you have a working Opera version, you need a way of getting back to it.

@jimunderscorep

I've been using this fix for a long time.

The latest Opera v56.0.3051.31 breaks the fix, with Opera opening in a 4:3 ratio window, and, so far, not maximizing with any control I can find. Full Screen mode is a useless alternative.

Frankly, it's easier just to roll back to v55 than try to communicate with developers.

I was having password problems today, one particular password, current Opera version, and the Synchronisation tool fixed it. It's under Settings > Basic. It's useful for keeping stuff matched between different machines, and one reason I keep using Opera despite the problems there can be with video codecs.

I know this is an old thread, but it keeps popping up on search engines. This answer works in August 2018, v55.0 under Linux.

@leocg And it's not a new problem. It has happened before. It's a pattern of repeated failure. Is there no web page on this site that you can link to, rather than just saying problem solved?

If it's a legal problem, I hope somebody has checked with a competent lawyer, because this wouldn't be the first time some competent professional has just been wrong about the law.

@denisftw I have lost count of the number of different solutions that have been put forward for these problems, all involving somehow obtaining a different version of libffmpeg.so which may not work with any other piece of software, and which can not be relied on to work with a particular version of Opera.

We're told it's because of patents, or mismatched library versions, or a library version needed specially for the new version of Opera which hasn't been released yet (and that all seems to miss the whole point of a library).

I am getting confused, and I am beginning to doubt if anyone else really knows a reliable answer. There seems to be too much of "It works for me so it must work for everyone."

I am trying to stay polite, but if "Tee-Emm" were still around and were dealing with computers, an award of The Most Highly Derogatory Order of the Irremovable Finger would already be in the post. Some of you deserve Season Tickets for your local ambulance service. The gabbling puts me in mind of a flock of chickens arguing over which end of the egg to to hatch from.

The most reliable fix seem to be to stop using Opera to read Twitter.

@avl So it's a fairly simple procedure, except that this library version might break other software. (It seems that I can set things up to either play a video in Opera, or in some other program, but not both.)
Why does it take you so long to explain it? Are you in the ffmpeg Fight Club or something?

We have a saying in Chicago, Mr. @bombacha . Once is happenstance, twice is coincidence, three times is enemy action.

@bombacha said in Opera 54.0.2952.51: another piece of crap! libffmpeg.so problem consists:

@zhochaka said in Opera 54.0.2952.51: another piece of crap! libffmpeg.so problem consists:

@bombacha My experience suggests that there may need to be an exact match of Opera and libffmpeg.so version

The version 0.31.4 didn't work with the previous version of Opera. It did work with the latest 54.0.2952.51 version.

That does make me wonder if the problem is more than just the wrong code being distributed.

Yes, a new lib doesn't work with previous releases, but a previous lib can work with new Opera releases. With new Opera releases many changes inside the code is done, fixes are made so the libffmpeg has to accommodate this changes that is some time incompatible with previous releases of Opera , it has nothing to do with wrong coding.

I think we may be slightly mixed up.

1: Why can't Opera work properly without getting a library-file from somewhere else? That suggests that, as distributed, it is supplied with the wrong code.

2: If the library has to be specially made to work with the opera calls, that feels as though the Opera code is badly written. It's missing the whole point of a library.

The first error should be easy to fix. The second feels a rather deeper problem.

@bombacha My experience suggests that there may need to be an exact match of Opera and libffmpeg.so version

The version 0.31.4 didn't work with the previous version of Opera. It did work with the latest 54.0.2952.51 version.

That does make me wonder if the problem is more than just the wrong code being distributed.