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 that
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.
//third_party/p
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 --show-pro
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 follow
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 0x55d294ee8ee7
Package: src:linux
Version: 4.15.17-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I upgraded to buster from stretch according to the wiki. I did abort the
configuration of minissdp by pressing Esc, when I was asked for the interface
IP. Upon reboot the screen stays
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 ca
Using files from the same architecture solved the problem for me.
One way of preventing this sort of thing would be to add a little footnote to
the installation guide, in section 4.3.2.2 [1], just after footnote 8, that the
iso image should be for the same architecture as the hd-media files.
The
I encounter the same bug: I prepared an USB stick with a squeeze debian
installer,
following the instructions at
http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html#usb-copy-flexible
I used the files from
http://http.us.debian.org/debian/dists/squeeze/main/installer-i386/current/images/hd-
Package: gmpc
Version: 0.15.1-1
Severity: serious
Justification: Policy 7.2
I've built this package using libcurl3 and it built fine, see below.
The dependency on libcurl4 renders this packages uninstallable.
See #430488
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
A
applied anywhere.
Thanks for pushing this forward a bit; we should get it fixed.
Joris.
PS. (and slightly off-topic) My personal opinion is that Perl has
utterly messed up Unicode handling. The documentation uses the terms
"Unicode" and "UTF8" as if they were interchangable.
fault. But the overflow is detected by Valgrind when
parsing an XML file with elements nested deeper than 512 levels.
Since it involves an input-triggered heap overflow, this is technically
a security vulnerability.
Joris.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
buffer overflow must still be fixed.
Since it involves an input-triggered heap overflow, this is
technically a security vulnerability.
Joris.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
And here is my smb.conf, I hope it helps.
An interesting observation is that the smbd crash occurs every Sunday
around 6:30 AM, some minutes after my /etc/cron.daily has run (which is
scheduled at 6:25 AM).
Greetings,
Joris
#
# Sample configuration file for the Samba suite for Debian GNU/Linux
15 matches
Mail list logo
