Hi all,
The status so far is that we have a patch that solves the problem by
re-enabling [tracing][1], but the reason that tracing was disabled in the
first place is because it depends on minified javascript. You can recompile
chromium yourself but this is not a permanent solution.
It seems
Hi all,
I have tried building chromium after applying
[tracing.patch](https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=945920;filename=enable-tracing.patch;msg=14)
Unfortunately, it failed early in the build process with the following
error:
ERROR Unresolved dependencies.
Hi Eloston,
Thanks for figuring out the cause of these random crashes! However, I was
unable to recompile chromium from source following your instructions. I got
the following error message at step 4b:
jj@telos:~/src/chromium-79.0.3945.79$ debian/rules get-orig-source
wget -nv
On Fri, Dec 27, 2019 at 01:29:13PM +0100, Stefan Bühler wrote:
Hi,
yes, you are right, my patch only fixes the task manager crash.
I now took a look at all backtraces, and all apart the first one
(probably older version?) seem to be the same "other" instance:
--- 8< ---
I am not quite
I have attached the output of `chromium --debug` after reading the
instructions in /usr/share/doc/chromium/README.Debian and installing the
chromium-dbgsym package. This always crashes on startup, not randomly, so
I probably did something wrong.
Any help would be appreciated.
Gr,
JJ
# Env:
#
Dear maintainer,
I experience the same random crashes with chromium 79.0.3945.79-1. This is
the console output from the moment of crashing:
Received signal 11 SEGV_MAPERR
#0 0x55d293b7ca99
#1 0x55d293ac60a6
#2 0x55d293b7b293
#3 0x55d293b7ca16
#4 0x7f3ca2883510
#5
I found the problem: There is an error in my Perl installation. After
upgrading I didn't replace the Perl interpreter used by local::lib. I
solved the problem by manually removing the directory $HOME/perl5
Sorry for bugging you dear maintainers with a problem unrelated to
apt-file. This bug
7 matches
Mail list logo
