Dev1 Galaxy Forum / Chromium after upgrade - Jessie to Ascii

Re: Chromium after upgrade - Jessie to Ascii

dummy@example.com (Geoff 42) — Sun, 08 Apr 2018 05:58:47 +0000

msi wrote:

Geoff 42 wrote:
After upgrading from Jessie to Ascii, the Chromium package was held back.
Using apt-get dist-upgrade usually solves that kind of problem for me.

I had run apt-get dist-upgrade several times and Chromium was still held back. It was the apt-get autoremove which finally allowed Chromium to be upgraded. I failed to spot which package was causing the dependency problem.

Geoff

Re: Chromium after upgrade - Jessie to Ascii

dummy@example.com (msi) — Sat, 07 Apr 2018 16:08:31 +0000

Geoff 42 wrote:

After upgrading from Jessie to Ascii, the Chromium package was held back.

Using apt-get dist-upgrade usually solves that kind of problem for me.

Re: Chromium after upgrade - Jessie to Ascii

dummy@example.com (GNUser) — Fri, 06 Apr 2018 19:24:04 +0000

Hi, Geoff42. I'm on a fully up-to-date ASCII here. I mostly use firefox but do have chromium 64.0.3282.119-1~deb9u1, which I use as a backup browser. I installed ASCII from scratch and didn't have to do anything special to get that version of chromium. I have never had this version of chromium give off any errors or ask me to reload, not even when using Google maps.

Hopefully it will be smooth sailing for you and the error will not return. If it does, I will be happy to try to help.

Chromium after upgrade - Jessie to Ascii

dummy@example.com (Geoff 42) — Fri, 06 Apr 2018 14:14:53 +0000

After upgrading from Jessie to Ascii, the Chromium package was held back. There were also a large number of packages which could be removed with apt-get autoremove. I had a quick look through these and could not see anything which might cause a problem. Doing the autoremove seemed to go smoothly, but had the side effect that Chromium could be upgraded, which I did and am now on 64.0.3282.119-1~deb9u1. Chromium does run, but I have had a couple of errors, while looking at Google maps, suggesting that I reload. It seems to have settled down a bit now and I can't reproduce the error message!

Geoff