Your message dated Sun, 3 Feb 2019 18:35:39 -0500
with message-id
<CANTw=mmjtnh4t19xbz0k+55ssmyuv9vb9arb1eeadn1fqqm...@mail.gmail.com>
and subject line Re: Bug#916984: chromium: Chromium won't stop cleaning
history. Killing process needed.
has caused the Debian Bug report #916984,
regarding chromium: Chromium won't stop cleaning history. Killing process
needed.
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.)
--
916984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 72.0.3626.7-3
Severity: important
Dear Maintainer,
Since a few days (possibly because of recent updates?), 'chromium won't stop
cleaning history;
the process is eternal and "killall chroumim" is required for stop the program.
Cheers,
Awtul
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE=es_ES:es (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.7-3
ii libasound2 1.1.7-2
ii libatk-bridge2.0-0 2.30.0-2
ii libatk1.0-0 2.30.0-1
ii libatomic1 8.2.0-13
ii libatspi2.0-0 2.30.0-5
ii libavcodec58 7:4.0.3-1
ii libavformat58 7:4.0.3-1
ii libavutil56 7:4.0.3-1
ii libc6 2.28-3
ii libcairo-gobject2 1.16.0-1
ii libcairo2 1.16.0-1
ii libcups2 2.2.10-3
ii libdbus-1-3 1.12.12-1
ii libdrm2 2.4.95-1
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat1 2.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-13
ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii libglib2.0-0 2.58.1-2
ii libgtk-3-0 3.24.2-3
ii libharfbuzz0b 2.2.0-1
ii libicu63 63.1-5
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.41-1
ii libopenjp2-7 2.3.0-1.1
ii libopus0 1.3-1
ii libpango-1.0-0 1.42.4-5
ii libpangocairo-1.0-0 1.42.4-5
ii libpci3 1:3.5.2-1
ii libpng16-16 1.6.34-2
ii libpulse0 12.2-2
ii libre2-4 20180901+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.2.0-13
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux2 0.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.7-3
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
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 awesome [notification-daemon] 4.2-5
ii chromium-sandbox 72.0.3626.7-3
ii dunst [notification-daemon] 1.3.2-1
ii fonts-liberation 1:1.07.4-9
ii libgl1-mesa-dri 18.2.7-1
ii libu2f-udev 1.1.6-1
ii notification-daemon 3.20.0-3
ii upower 0.99.9-2
Versions of packages chromium-sandbox depends on:
ii libatomic1 8.2.0-13
ii libc6 2.28-3
ii libgcc1 1:8.2.0-13
ii libstdc++6 8.2.0-13
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Dec 20, 2018 at 10:06 PM Awtul wrote:
> Version: 72.0.3626.7-3
[...]
> Since a few days (possibly because of recent updates?), 'chromium won't stop
> cleaning history;
I have not seen this. 72.0.3626.7 was an upstream development
version, and this is probably fixed now that a stable version of 72
has been uploaded. Please feel free to reopen if it is not fixed.
Best wishes,
Mike
--- End Message ---
