Your message dated Sun, 19 Feb 2017 19:53:39 -0500
with message-id
<CANTw=MNromMUWxZQ3e1PcsCF7C4wXn=remumzhf3ee1tu_y...@mail.gmail.com>
and subject line re: chromium: option --enable-remote-extensions does work
has caused the Debian Bug report #852398,
regarding chromium: option --enable-remote-extensions does work: extensions
cannot be enabled nor be installed
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.)
--
852398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852398
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 55.0.2883.75-6
Severity: normal
Dear maintainers,
remote extensions are disabled now by default
I understand that official chrome extensions such as Adblock Plus (or similar
ones) and non-official extensions can be enabled and can be installed only if
the
--enable-remote-extensions
command line option is used when launching chromium.
However, this behaviour is not observed: whether this command-line option is
used or not, no extension (official nor non-official) can be enabled nor can be
installed.
Besides, also irrespective of this option, annoying extensions such as
"Chromium PDF Viewer" cannot be disabled.
Is this the normal behaviour?
Browsing without Adblock Plus can be unsafe if one wants to keep one's mind
sound in the short term;)
Best,
Ara
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii libasound2 1.1.3-2
ii libatk1.0-0 2.22.0-1
ii libavcodec57 10:3.0-dmo4
ii libavformat57 10:3.0-dmo4
ii libavutil55 10:3.0-dmo4
ii libc6 2.24-9
ii libcairo2 1.14.8-1
ii libcups2 2.2.1-6
ii libdbus-1-3 1.10.14-1
ii libevent-2.0-5 2.0.21-stable-2.1
ii libexpat1 2.2.0-2
ii libflac8 1.3.2-1
ii libfontconfig1 2.11.0-6.7
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.3.0-4
ii libgdk-pixbuf2.0-0 2.36.4-1
ii libglib2.0-0 2.50.2-2
ii libgtk2.0-0 2.24.31-1
ii libharfbuzz0b 1.2.7-1+b1
ii libicu57 57.1-5
ii libjpeg62-turbo 1:1.5.1-2
pn libminizip1 <none>
ii libnspr4 2:4.12-6
ii libnss3 2:3.26.2-1
ii libpango-1.0-0 1.40.3-3
ii libpangocairo-1.0-0 1.40.3-3
ii libpng16-16 1.6.28-1
ii libpulse0 10.0-1
ii libre2-3 20170101+dfsg-1
ii libsnappy1v5 1.1.3-3
ii libstdc++6 6.3.0-4
ii libvpx4 1.6.1-2
ii libwebp6 0.5.2-1
ii libwebpdemux2 0.5.2-1
ii libx11-6 2:1.6.4-2
ii libx11-xcb1 2:1.6.4-2
ii libxcb1 1.12-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.8-2
ii libxml2 2.9.4+dfsg1-2.2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.29-2
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.3-1
ii x11-utils 7.7+3
ii xdg-utils 1.1.1-1
ii zlib1g 1:1.2.8.dfsg-4
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-2
Versions of packages chromium suggests:
pn chromium-driver <none>
ii chromium-l10n 55.0.2883.75-6
pn chromium-shell <none>
pn chromium-widevine <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
version: 56.0.2924.76-1
The option now works as intended.
Best wishes,
Mike
--- End Message ---
