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 file in /etc/chromium.d is obsolete.
> 
> Best wishes,
> Mike

Should does not mean must but I intend to remove it anyway.

Markus



signature.asc
Description: OpenPGP digital signature


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-origin is now a transitional package.  It should clean
up its conffiles in /etc/chromium.d when removed.

Best wishes,
Mike



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 webext-.

But the culprit was chromium-ublock-origin which was only
uninstalled, but not purged. After purging
chromium-ublock-origin, the message is gone.

It would be nice, if chromium could be a little bit more
verbose with this dialog :)

Cheers & thanks for the help!



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 with a default install. Would you mind trying
with it removed?

Best wishes,
Mike



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 causes this.

I don't think I have any extensions installed:

$ dpkg --get-selections webext-\*
$

Still, under chrome://extensions/, I see three extensions:

 - Chromium PDF Viewer
 - CryptoTokenExtension
 - GNOME Shell integration

The first two have a "Remove" button, but pressing such a button
does not have any other effect than flashing the button. It does
not remove the extension.

As I wrote before, I experience this is with a newly created
user account, so there shouldn't be any messed config.



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
> > is missing or unreadable
> > OK

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 causes this.

Best wishes,
Mike



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 disappears after around 1 s. I'm not aware of any
further problems related to the warning, but it is confusing
and annoying, esp. to less "technical" users, who fear their
whole system is broken.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')

Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8), 
LANGUAGE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  72.0.3626.109-1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-4
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.2.0-20
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1-1
ii  libavformat587:4.1-1
ii  libavutil56  7:4.1-1
ii  libc62.28-7
ii  libcairo-gobject21.16.0-2
ii  libcairo21.16.0-2
ii  libcups2 2.2.10-3
ii  libdbus-1-3  1.12.12-1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.2.0-20
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42-1
ii  libopenjp2-7 2.3.0-1.1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.36-5
ii  libpulse012.2-3
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.2.0-20
ii  libva2   2.4.0-1
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  72.0.3626.53-1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 72.0.3626.53-1
ii  fonts-liberation 1:1.07.4-9
ii  gnome-shell [notification-daemon]3.30.1-2
ii  libgl1-mesa-dri  18.3.2-1
ii  libu2f-udev  1.1.7-1
ii  notification-daemon  3.20.0-4
ii  upower   0.99.9-3
ii  xfce4-notifyd [notification-daemon]  0.4.3-1

Versions of packages chromium-sandbox depends on:
ii  libatomic1  8.2.0-20
ii  libc6   2.28-7
ii  libgcc1 1:8.2.0-20
ii  libstdc++6  8.2.0-20

-- no debconf information