Your message dated Thu, 15 Mar 2018 18:21:50 -0400
with message-id
<CANTw=mnrkgzzg_q8rnwag5yuuwvdqcf6e-rk22_vivxu7tr...@mail.gmail.com>
and subject line Re: Bug#890954: closed by Michael Gilbert
<mgilb...@debian.org> (Bug#890954: fixed in chromium-browser 65.0.3325.146-2)
has caused the Debian Bug report #890954,
regarding Adblockers fail to start
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.)
--
890954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 65.0.3325.74-1 and others
Chromium from the Debian sid and experimental repository causes
adblockers to fail to start. Install one of these:
https://chrome.google.com/webstore/search/adblock
I have signal 11 SEGV_MAPERR when logging
is enabled:
xfce@ryzen5pc:~/Downloads/git$ chromium --enable-logging
--v=1
[7464:7494:0227/134956.921431:ERROR:in_progress_cache_impl.cc(93)]
Could not read download entries from file because there was a read
failure.
[7464:7505:0227/134957.071911:ERROR:connection_factory_impl.cc(379)]
Failed to connect to MCS endpoint with error -21
[7518:7518:0227/134957.092703:ERROR:sandbox_linux.cc(375)]
InitializeSandbox() called with multiple threads in process
gpu-process. Received signal 11 SEGV_MAPERR 0000ffffff00 #0
0x560ef24e837e <unknown> #1 0x560ef0d46f4f <unknown> #2 0x560ef24e8737
<unknown> #3 0x7f8884312f50 <unknown> #4 0x7f8878909010 <unknown> #5
0x7f88792369be std::__cxx11::basic_string<>::compare() #6
0x560ef300eb50 <unknown> #7 0x560ef216dc1d <unknown> #8 0x560ef2178a95
<unknown> #9 0x560ef3fd54ee <unknown>
#10 0x560ef3e348d4 <unknown>
#11 0x560ef3e3f413 <unknown>
#12 0x560ef4fb737f <unknown>
#13 0x560ef4fb7b33 <unknown>
#14 0x560ef4e94a8d <unknown>
#15 0x560ef1903ad7 <unknown>
#16 0x560ef198ce7e <unknown>
#17 0x560ef198db76 <unknown>
#18 0x3a0be188431d <unknown>
r8: 00007fff17cd70f8 r9: 00007fff17cd7120 r10: 696c6769626b6b67 r11:
6e6f63692f6d6f64 r12: 00007fff17cd70d8 r13: 0000560ef58bc746 r14:
00007fff17cd7298 r15: 00007fff17cd7148 di: 00000000ffffff00 si:
0000560ef58bc746 bp: 0000000000000001 bx: 0000560ef7785ee8 dx:
0000000000000001 ax: 0000000000000001 cx: 0000000000000746 sp:
00007fff17cd6f88 ip: 00007f8878909010 efl: 0000000000010246 cgf:
002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk:
0000000000000000 cr2: 00000000ffffff00 [end of stack trace] Calling
_exit(1). Core file will not be generated.
I made a bug report to bugs.chromium.org and they wrote:
"
We have no control over how Debian builds and distributes their flavor
of Chromium. Please report this bug to Debian instead. "
--- End Message ---
--- Begin Message ---
version: 65.0.3325.146-2
--- End Message ---
