Control: found -1 chromium-shell/63.0.3239.84-1~deb9u1
Control: tag -1 stretch
> Source: chromium-browser
> Source-Version: 60.0.3112.72-1
>
> We believe that the bug you reported is fixed in the latest version of
> chromium-browser
Sorry, but it seems to me, that this bug is not fixed in stable
(Stretch) and its chromium-shell version 63.0.3239.84-1~deb9u1:
$ chromium-shell
[25398:25398:0128/041122.890412:311365848311:FATAL:v8_initializer.cc(248)]
Couldn't mmap v8 natives data file, status code is 1
#0 0x55a1fe5d0eb6 <unknown>
#1 0x55a1fe5e81da <unknown>
#2 0x55a1ff27181d <unknown>
#3 0x55a1fe0c5e79 <unknown>
#4 0x55a1fefaf635 <unknown>
#5 0x55a1fd950e71 <unknown>
#6 0x55a1fd611c58 <unknown>
#7 0x7f2c139822b1 __libc_start_main
#8 0x55a1fd6158ea _start
Aborted
$ type chromium-shell
chromium-shell is hashed (/usr/bin/chromium-shell)
$ strace chromium-shell
<...>
open("/usr/bin/snapshot_blob.bin", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/bin/natives_blob.bin", O_RDONLY) = -1 ENOENT (No such file or
directory)
<...>
open("/usr/bin/content_shell.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 EACCES
(Permission denied)
<...>
Did I miss something?
