Bug#923001: error message on start

2019-02-24 Thread Markus Koschany
Control: severity -1 important On Sat, 23 Feb 2019 21:20:42 -0500 Michael Gilbert wrote: > control: severity -1 serious > > Increasing severity since policy 10.7.3 is violated: > > "Obsolete configuration files without local changes should be removed > by the package during upgrade." > > The f

Bug#923001: error message on start

2019-02-23 Thread Michael Gilbert
control: severity -1 serious Increasing severity since policy 10.7.3 is violated: "Obsolete configuration files without local changes should be removed by the package during upgrade." The file in /etc/chromium.d is obsolete. Best wishes, Mike

Bug#923001: error message on start

2019-02-23 Thread Michael Gilbert
control: notforwarded -1 control: reassign -1 chromium-ublock-origin On Sat, Feb 23, 2019 at 8:31 PM W. Martin Borgert wrote: > But the culprit was chromium-ublock-origin which was only > uninstalled, but not purged. After purging > chromium-ublock-origin, the message is gone. chromium-ublock-ori

Bug#923001: error message on start

2019-02-23 Thread W. Martin Borgert
On 2019-02-23 18:21, Michael Gilbert wrote: > It likely relates to the GNOME shell extension, though it may not. I > am not able to reproduce with a default install. Would you mind trying > with it removed? chrome-gnome-shell was installed, indeed — I only searched for packages starting with webe

Bug#923001: error message on start

2019-02-23 Thread Michael Gilbert
On Sat, Feb 23, 2019 at 1:58 PM W. Martin Borgert wrote: > Still, under chrome://extensions/, I see three extensions: > > - Chromium PDF Viewer > - CryptoTokenExtension > - GNOME Shell integration It likely relates to the GNOME shell extension, though it may not. I am not able to reproduce wit

Bug#923001: error message on start

2019-02-23 Thread W. Martin Borgert
(I write this mainly to document the bug. It's certainly not worth to invest much time on it.) On 2019-02-23 12:18, Michael Gilbert wrote: > This seems related to this upstream issue. Buggy extensions can cause > this. You could try removing extensions one at a time to determine > which one caus

Bug#923001: error message on start

2019-02-23 Thread Michael Gilbert
control: severity -1 minor control: forwarded -1 http://crbug.com/724826 On Fri, Feb 22, 2019 at 4:36 PM W. Martin Borgert wrote: > When I start chromium as a newly added user (no chromium config > is present in $HOME) I get a warning dialog: > > > Failed to load extension from: . Manifest file >

Bug#923001: error message on start

2019-02-22 Thread W. Martin Borgert
Package: chromium Version: 72.0.3626.109-1 When I start chromium as a newly added user (no chromium config is present in $HOME) I get a warning dialog: > Failed to load extension from: . Manifest file > is missing or unreadable > OK The warning disappe