Your message dated Sun, 3 Feb 2019 21:09:41 -0500
with message-id
<CANTw=MNf+mVhjvGo4z7xa-QgA5Qo5oifTZNJJJT=2v1gteq...@mail.gmail.com>
and subject line Re: Bug#916725: chromium: Extensions which access Google
Bookmarks fail
has caused the Debian Bug report #916725,
regarding chromium: Extensions which access Google Bookmarks fail
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 ow...@bugs.debian.org
immediately.)
--
916725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 71.0.3578.80-1~deb9u1
Severity: important
Dear Maintainer,
Extensions which attempt to access Google (not chrome) bookmarks no longer
function. This is a regression introducted since 69.0.3497.92-1~deb9u1.
Example extensions which now fail:
*
https://chrome.google.com/webstore/detail/goomarks-browser-for-goog/oknllbfkmapccinochelgmcdjhlgfnik?hl=en-GB
*
https://chrome.google.com/webstore/detail/%EA%B5%AC%EA%B8%80-%EB%B6%81%EB%A7%88%ED%81%AC-%ED%8A%B8%EB%A6%AC/ofppcpdgnpnmlmellfphhehmhkafbgmm?hl=en-GB
I don't believe this has yet been reported upstream.
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (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-5
ii libatk1.0-0 2.22.0-1
ii libatomic1 6.3.0-18+deb9u1
ii libatspi2.0-0 2.22.0-6+deb9u1
ii libavcodec-extra57 7:3.2.12-1~deb9u1
ii libavformat57 7:3.2.12-1~deb9u1
ii libavutil55 7:3.2.12-1~deb9u1
ii libc6 2.24-11+deb9u3
ii libcairo2 1.14.8-1
ii libcups2 2.2.1-8+deb9u2
ii libdbus-1-3 1.10.26-0+deb9u1
ii libdrm2 2.4.74-1
ii libevent-2.0-5 2.0.21-stable-3
ii libexpat1 2.2.0-2+deb9u1
ii libflac8 1.3.2-1
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.2
ii libgcc1 1:6.3.0-18+deb9u1
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2
ii libglib2.0-0 2.50.3-2
ii libgtk2.0-0 2.24.31-2
ii libicu57 57.1-6+deb9u2
ii libjpeg62-turbo 1:1.5.1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.12-6
ii libnss3 2:3.26.2-1.1+deb9u1
ii libopenjp2-7 2.1.2-1.1+deb9u2
ii libopus0 1.2~alpha2-1
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libpangoft2-1.0-0 1.40.5-1
ii libpci3 1:3.5.2-1
ii libpng16-16 1.6.28-1
ii libpulse0 10.0-1+deb9u1
ii libre2-3 20170101+dfsg-1
ii libsnappy1v5 1.1.3-3
ii libstdc++6 6.3.0-18+deb9u1
ii libvpx4 1.6.1-3+deb9u1
ii libwebp6 0.5.2-1
ii libwebpdemux2 0.5.2-1
ii libwebpmux2 0.5.2-1
ii libx11-6 2:1.6.4-3+deb9u1
ii libx11-xcb1 2:1.6.4-3+deb9u1
ii libxcb1 1.12-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.14-1+deb9u2
ii libxdamage1 1:1.1.4-2+b3
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-2.2+deb9u2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.29-2.1
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.3-1
ii x11-utils 7.7+3+b1
ii xdg-utils 1.1.1-1+deb9u1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-2
ii libgl1-mesa-dri 13.0.6-1+b2
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
pn chromium-widevine <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Dec 31, 2018 at 6:31 PM Michael Gilbert wrote:
> enable_one_click_signin is set to false starting with version 70 to
> prevent background interfacing with google services. It is the most
> likely cause here. Other users expect chromium to not interface with
> google's services, so you would need to debate them about whether or
> not this should be enabled. I am inclined to leave it disabled.
I've decided to leave it disabled.
Best wishes,
Mike
--- End Message ---
