[Desktop-packages] [Bug 1719200] Re: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2017-11-06 Thread Olivier Tilloy
Closing the report as it's not an actual bug in chromium. Feel free to re-open if you're still seeing the issue. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed

[Desktop-packages] [Bug 1719200] Re: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2017-11-06 Thread Olivier Tilloy
Please try the following command in a terminal, and paste the output here: sudo apt-get install --reinstall chromium-browser -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1719200] Re: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2017-10-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1719200] Re: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2017-09-24 Thread Apport retracing service
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1719200 Title: package chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300 failed to