Bug#922431: Upstream is confused about Tracing consisting on non-source JS

On Fri, 2 Aug 2019 20:57:37 -0400 Michael Gilbert wrote: > The sourceless files are in third_party/catapult/tracing, which is now > stripped out of the debian source package. Looking through http://commondatastorage.googleapis.com/chromium-browser-official/chromium-76.0.3809.71-lite.tar.xz (the

Bug#741295: libssl: Improper release of read buffers when SSL_MODE_RELEASE_BUFFERS set

Package: libssl1.0.0 Version: 1.0.1f-1 Severity: important File: libssl When using libssl from multiple threads with SSL_MODE_RELEASE_BUFFERS enabled, it seems that read buffers are being improperly released. Under load, I'm seeing the errors below. This bug has already been reported to OpenSSL,

Bug#717105: kupfer: segfault using dbus

Package: kupfer Version: 0+v208-2 Severity: important Kupfer segfaults when using python-dbus; a change to fix was already committed upstream but has not yet been pulled into Debian. Right now, Kupfer is unusable as it segfaults quickly after starting. Refs:

Bug#551647: And I got it to work...

When I use fusion-icon to launch compiz, it loads it with the following options: compiz.real --ignore-desktop-hints --sm-disable --indirect-rendering --replace ccp However, if I load compiz by myself without --sm-disable, it loads and functions just fine. This could just be me...

Bug#551647: It's libglib2.0-2.22.2-2

From /var/log/messages: kernel: [ 1848.349475] compiz.real[5158]: segfault at 7f15bf79fd68 ip 7f15bf9e1faa sp 7fffd4dce240 error 4 in libglib-2.0.so.0.2200.2[7f15bf9a4000+c4000] This problem is being reported everywhere, and all of them are dealing with the same glib version. I