Your message dated Sat, 10 Feb 2018 22:12:34 -0500
with message-id
<CANTw=mp9j5tcvpgqfsu+su_yomwzmcbouknj0z0zp7pnh9z...@mail.gmail.com>
and subject line Re: Bug#864565: fixed in chromium-browser 60.0.3112.72-1
has caused the Debian Bug report #864565,
regarding chromium-shell: Couldn't mmap v8 natives data file, status code is 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 ow...@bugs.debian.org
immediately.)
--
864565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium-shell
Version: 59.0.3071.86-1
Severity: grave
Justification: renders package unusable
--8<---------------cut here---------------start------------->8---
$ chromium-shell
[27049:27049:0610/210346.749391:144625948825:FATAL:v8_initializer.cc(249)]
Couldn't mmap v8 natives data file, status code is 1
#0 0x564ed78bb026 <unknown>
#1 0x564ed78d236e <unknown>
#2 0x564ed891af15 <unknown>
#3 0x564ed7250f01 <unknown>
#4 0x564ed83ba060 <unknown>
#5 0x564ed68b1fc1 <unknown>
#6 0x564ed65c3bd0 <unknown>
#7 0x7faf84cfb2b1 __libc_start_main
#8 0x564ed65c6c8a _start
Aborted
--8<---------------cut here---------------end--------------->8---
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable'), (70, 'unstable'), (60, 'testing'), (50,
'experimental'), (40, 'oldstable')
Architecture: amd64
(x86_64)
Kernel: Linux 4.9.0-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
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-shell depends on:
ii libasound2 1.1.3-5
ii libatk1.0-0 2.22.0-1
ii libavcodec-extra57 7:3.2.5-1
ii libavformat57 7:3.2.5-1
ii libavutil55 7:3.2.5-1
ii libc6 2.24-11
ii libdbus-1-3 1.11.12-1
ii libdrm2 2.4.81-1
ii libevent-2.0-5 2.0.21-stable-3
ii libexpat1 2.2.0-2
ii libflac8 1.3.2-1
ii libfontconfig1 2.12.1-0.1
ii libgcc1 1:7.1.0-6
ii libglib2.0-0 2.53.1-1
ii libharfbuzz0b 1.4.2-1
ii libicu57 57.1-6
ii libjpeg62-turbo 1:1.5.1-2
ii libminizip1 1.1-5
ii libnspr4 2:4.14-1
ii libnss3 2:3.30.2-1
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libpng16-16 1.6.29-2
ii libpulse0 10.0-1
ii libre2-3 20170101+dfsg-1
ii libsnappy1v5 1.1.4-1
ii libstdc++6 7.1.0-6
ii libvpx4 1.6.1-3
ii libwebp6 0.6.0-1
ii libwebpdemux2 0.5.2-1
ii libx11-6 2:1.6.4-3
ii libx11-xcb1 2:1.6.4-3
ii libxcb1 1.12-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.14-1+b4
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
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 zlib1g 1:1.2.8.dfsg-5
chromium-shell recommends no packages.
chromium-shell suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Jan 29, 2018 at 11:20 PM, Dmitry Alexandrov wrote:
> Did I miss something?
Yes, you missed that the BTS already represents the bug as being
unfixed in the stable release.
Best wishes,
Mike
--- End Message ---
