Siduction Forum

Siduction Forum => Upgrade Warnings => Thema gestartet von: drb in 2018/10/15, 11:39:52

Titel: Problem with Chromium update
Beitrag von: drb in 2018/10/15, 11:39:52
See bug report at :https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911056 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911056)
Titel: Re: Problem with Chromium update
Beitrag von: Kan in 2018/10/15, 19:15:08
If you have issues with installing it, remove the current Chromium first, then install. I think they have changed the location to /etc/Chromium which for whatever reasons caused issues with the previous chromium installation, so remove it first.
Also, users running gnome, may have to uninstall chrome-gnome-shell and then reinstall it after you install chromium. I think there are some critical bugs with chrome-gnome-shell also ...maintainer needs to update.
Titel: Re: Problem with Chromium update
Beitrag von: drb in 2018/10/15, 19:35:10
I've tried that, but it won't reinstall.dpkg: warning: chromium: conffile '/etc/chromium' is not a plain file or symlink (= '/etc/chromium')
dpkg: error processing archive /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack):
trying to overwrite directory '/etc/chromium' in package net.downloadhelper.coapp 1.2.4 with nondirectory
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Titel: Re: Problem with Chromium update
Beitrag von: Kan in 2018/10/15, 19:40:27
That is odd. I got those same errors at first. Make sure you uninstall all Chromium parts, everything that starts with "Chromium-", chromium-common, etc. Then apt-get install chromium.
Titel: Re: Problem with Chromium update
Beitrag von: Baggi in 2018/10/15, 22:46:37
Problem with Debian Sid and upgrade Chromium.  "apt purge chromium*" befor, same problem.
Es wurden 42,5 MB in 23 s geholt (1.850 kB/s).                                 
Vormals nicht ausgewähltes Paket chromium-common wird gewählt.
(Lese Datenbank ... 168663 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../chromium-common_70.0.3538.54-2_amd64.deb ...
Entpacken von chromium-common (70.0.3538.54-2) ...
Vorbereitung zum Entpacken von .../chromium_70.0.3538.54-2_amd64.deb ...
Entpacken von chromium (70.0.3538.54-2) ...
dpkg: Warnung: chromium: Conffile »/etc/chromium« ist keine gewöhnliche Datei oder symbolischer Link (= »/etc/chromium«)
dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack):
Versuch, Verzeichnis »/etc/chromium« in Paket chrome-gnome-shell 10.1-1 mit Nichtverzeichnis zu überschreiben
dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet
Fehler traten auf beim Bearbeiten von:
/var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Titel: Re: Problem with Chromium update
Beitrag von: drb in 2018/10/15, 23:05:50
ZitatThat is odd. I got those same errors at first. Make sure you uninstall all Chromium parts, everything that starts with "Chromium-", chromium-common, etc. Then apt-get install chromium.
Still wouldn't reinstall after chromium-common removed. Also removed the one package that linked to /etc/chromium
Titel: Re: Problem with Chromium update
Beitrag von: Kan in 2018/10/16, 04:45:38
Sorry guys that didn't work. It worked for me, but I use Budgie desktop so maybe that makes a difference. Regardless, there are bug reports against Chromium, so it is a waiting game for now unless someone else has a suggestion. Hopefully the maintainers will release a fix soon.
Titel: Re: Problem with Chromium update
Beitrag von: Mte90 in 2018/10/16, 12:44:02
I removed manually the /etc/chromium because has only the file to use the plasma-browser-integration that I us only on firefox and not on chrome.With that removal there wasn't problem on proceed.
Titel: [SOLVED] Re: Problem with Chromium update
Beitrag von: drb in 2018/10/17, 17:50:20
The latest version of Chromium has been fixed to solve the problem.