As you can see the problem is limited to chromium. I’ve tried to view the same page from another, different user account, and the problem is still there, so I can safely rule out browser cache or local configuration.
Apparently the problem appears with some video formats only, i.e. Vimeo videos are affected but Youtube plays nicely as usual.
If needed, here are some info about my system packages.
sbweb@opensuse-kde:~> LANG=C sudo zypper search -si chromium
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-----------------------+---------+-------------------+--------+------------------------
i+ | chromium | package | 70.0.3538.67-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
i+ | chromium-ffmpeg-extra | package | 69.0.3497.100-2.2 | x86_64 | packman
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
I think that it could be related to the different versions of these two packages, but it is just a guess.
Ok, I see that at least part of your multi-media related packages is from Packman. But that does not prove (and you did to confirm) that you did the Vendor switch to Packman.
Even when you did, it is maybe useful do repeat it so that you (and we) are 1000% certain that it is done.
Thanks for the confirmation. It is always difficult to assess this and just assuming that the other partner in the discussion has the same view of the world is dangerous
No problem, an extra confirmation doesn’t hurt. Thanks to you for your help.
I’ll try to see if thew problem will solve when the codec package will be updated to the same version as Chromium.
Meanwhile I’m re-discovering Firefox and it really makes me want to switch back, unfortunately for web design and development Chrome is a must because of its market share.
This means you locked packages to their current version/status ( i.e. not installed ), and has nothing to do with the thing Henk suggested, i.e. the vendor switch. Doing so will definitely have you run into trouble since it involves KDE packages, since these also depend on plasma and KDE frameworks packages which need to be coherent. F.e. if Kontact is used and konversation is installed, Kontact and konversation’s versions won’t match and will not be packages built against the same version libs.
EDIT: read akregator instead of konversation. Or knotes.
I think something on your system is messed up as Knurpht said locking some of those packages basically locks a lot of dependencies and as you’re on TW kde is probobly borked you should unlock the kde packages and redo an update
and I can’t understand why have you locked the ati video driver xf86-video-ati I assume you’re using the radeon driver but as a general rule assumption leads to errors unlock most of those packages then update your system
one more thing chromium-ffmpeg-extra is not needed or used by Chromium any more it’s needed for chromium based browsers like Opera or Vivaldi so unless you’re using Opera or Vivaldi remove that package
Please look at the command that I gave to the terminal, that was a correct vendor change to the packman repo: “sudo zypper dup --from packman”; those packages were already locked before.
Please note that the packages are locked in an “uninstalled” status, because I don’t need them and I don’t want them reinstalled everytime that I update my system.
The list of the locked packages is just an information that zypper outputs everytime that it is run. I have those locked since I started using TW more than a year ago, and never had any kind of problem related to them being locked. Those mainly are programs that I don’t need, fonts that I don’t use, and that I removed to reduce the clutter in my system.
The problem with Chromium started just some days ago, when those packages were locked by a way larger amount of time, and I don’t understand your reasoning about trouble being caused by locked KDE packages. The workspace and the DE are working fine, I’m having problems with Chromium, that is not a KDE project.
To answer about the locked ati driver, I had removed it beacuse it was giving problems that were causing the system to be unusable; while the radeon one is working fine and without causing any trouble.
