Your message dated Wed, 26 Apr 2017 07:19:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#861079: chromium: Remote extensions not enabled by
default in 58.0.3029.81-1
has caused the Debian Bug report #861079,
regarding chromium: Remote extensions not enabled by default in 58.0.3029.81-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
861079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861079
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 58.0.3029.81-1
Severity: normal
Dear Michael,
I see from the changelog that starting from 58.0.3029.68-1 the remote
extensions should be enabled by default. First of all, thanks for
bringing back the old behavior. Unfortunately it doesn't seem to work
yet: chromium still need to be launched with --enable-remote-extensions
in order to get the extensions working.
Paride
--- End Message ---
--- Begin Message ---
On 2017-04-26 01:55, Michael Gilbert wrote:
> control: tag -1 moreinfo, unreproducible
>
>> chromium still need to be launched with --enable-remote-extensions
>> in order to get the extensions working.
>
> That is expected and /etc/chromium.d/extensions should cause it to be
> set automatically. Have you modified the chromium launcher script or
> anything in /etc/chromium.d that would prevent that from happening?
Definitely my fault.
--- End Message ---
