Hi, I have been using Chromium for a while now. Lately, I got the feeling that an increasing number of websites don’t work (any more). When that happened before, I opened either Firefox or Chrome to use that website.
Last time I had to do that, I realised that Chrome is now at v32 while Opensuse’s Chromium is still at v31. That’s strange because I could swear that Chromium used to be ahead a version number compared to Chrome.
Anyhow, so I looked for a newer version but except for a cutting-edge (and oft-broken) repository on OBS, the latest Chromium supported by Opensuse seems to be indeed Version 31.
Can that be right? And if yes - why is opensuse delivering an outdated Chromium?
current version of Chromium in OSS is 31.0.1650.63-13.7 with a build date of 08 January 2014 so it isn’t really that old.
I find it incredible that you are coming across pages incompatible with Chromium. I can’t remember the last time I had any problems.
The oss repo is only ever going to give you stable, tested applications. You are not usually going to find cutting edge stuff in there.
You can get a newer version of Chromium from here but I doubt it is going to fix your website compatibility issues. That is more likely a corrupt install of Chromium causing your problems.
I share your disbelief. It did not happen for a long time, but now it does. Hence the search for a new version - Chrome (now in v32) displays the sites in question beautifully. Chromium (even with a different user’s profile) does not, so I doubt it’s a corrupt profile on my end.
The stable version of CHROME is 32 so at least Chromium should be at that level, too. The build date doesn’t matter, the date of the source does - and it’s not the latest one.
I am not absolutely sure which repo I used previously (i.e. before the update to 13.1) but I seem to remember that Chromium was typically one version ahead of Chrome.
Well, it looks like v33 is the latest “released” version of Chromium. But no matter if v32, v33 or v34, am I the only one using Chromium on OpenSuse? Or just the only one bothered by having to use an outdated version? Or is everyone compiling for themselves :\
On Wed 29 Jan 2014 01:46:01 AM CST, michbona wrote:
farcusnz;2619610 Wrote:
> current version of Chromium in OSS is 31.0.1650.63-13.7 with a build
> date of 08 January 2014 so it isn’t really that old.
>
> I find it incredible that you are coming across pages incompatible
> with Chromium. I can’t remember the last time I had any problems.
>
> The oss repo is only ever going to give you stable, tested
> applications. You are not usually going to find cutting edge stuff in
> there.
>
>
I share your disbelief. It did not happen for a long time, but now it
does. Hence the search for a new version - Chrome (now in v32) displays
the sites in question beautifully. Chromium (even with a different
user’s profile) does not, so I doubt it’s a corrupt profile on my end.
The stable version of CHROME is 32 so at least Chromium should be at
that level, too. The build date doesn’t matter, the date of the source
does - and it’s not the latest one.
I am not absolutely sure which repo I used previously (i.e. before the
update to 13.1) but I seem to remember that Chromium was typically one
version ahead of Chrome.
Hi
Use the Chromium from the packman repository, AFAIK there were some
more licensing issues, stable (less ffmpeg support) is still there,
stable, beta and devel on packamn. You need to search the development
ML archive to see all the details from I think September last year…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On Wed 29 Jan 2014 01:56:01 AM CST, michbona wrote:
Well, it ‘looks’ (http://www.chromium.org/developers/calendar) like v33
is the latest “released” version of Chromium. But no matter if v32, v33
or v34, am I the only one using Chromium on OpenSuse? Or just the only
one bothered by having to use an outdated version? Or is everyone
compiling for themselves :\
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Malcolm, thanks for setting me on the right track. This is what I did to finally resolve this issue:
checked the link to the packman repository. Got excited because they seemed to offer v32 (stable), v33 (beta) and v34 (dev)
did a one-click install of v33 - just to realise that the one-click .ymp file is seriously outdated and contains no reference to a certain OpenSuse 13.1
in the process realised that really all packman offers is the chromium-ffmpeg package (rather than the browser itself)
re-read your post and searched the ML for some background
as it turns out, OpenSuse (not Packman) does ship a newer Chromium, but only in the network:chromium repository. Which is not a default repository.
if you search software.opensuse.org this repository is listed under “unstable packages”. Which is ironic - you need an unstable package to get a stable browser
in order to get support for some of the proprietary multimedia formats you need to install the above-mentioned chromium-ffmpeg from Packman
BUT: Packmans chromium-ffmpeg goes with the chromium from the standard Opensuse repo (v31).
So, in a nutshell:
to get the latest stable chromium, you need Opensuse network:chromium repo.
for that version, you won’t get the full ffmpeg support
for chromium-beta and chromium-dev all is well - get the browser from network:chromium and chromium-ffmpeg from Packman.
Michbona and Malcolm, thank you for pointing the rest of us in the right direction! It shouldn’t be this difficult to update to the current stable version of the open-source version of Chrome. But at least it’s available somewhere. Thanks again.