Bug#998108: firefox freezes shortly after start

2021-11-11 Thread
On Thu, 11 Nov 2021 23:06:44 +1100 =?UTF-8?B?4oCN5bCP5aSq?= wrote: > So either the change needs to be backported to v94, or we'll just have to wait > until v95 (or compile the browser ourselves) I was a bit adventurous and tried doing a binary patch on the current debian version (94.0-1), and

Bug#998108: firefox freezes shortly after start

2021-11-11 Thread
I narrowed down the freeze to the cubeb pulse code (part of the audio library firefox uses), and I found that it was actually fixed almost a month ago: https://github.com/mozilla/cubeb-pulse-rs/pull/72 It's already been merged into firefox on-track for v95:

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-10-04 Thread
On Sun, 3 Oct 2021 12:33:48 +0100 Simon McVittie wrote: > On Sat, 02 Oct 2021 at 20:48:55 +1000, ‍小太 wrote: > > What I can add is from reading the documentation of > > g_quark_from_static_string() > > (https://docs.gtk.org/glib/func.quark_from_static_string.html) > >

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-10-03 Thread
On Sun, 3 Oct 2021 at 20:47, Ryan Thoryk wrote: > > When I had jack dump out it's module filenames during library load, it > only appeared to load jack_firewire once. The clue as to what's > happening is that valgrind reports "Bad permissions for mapped region", > if you look at the function,

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-10-02 Thread
Since the offending code seems to be present upstream in the glibmm-2-66 branch, I've also reported it upstream: https://gitlab.gnome.org/GNOME/glibmm/-/issues/96

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

2021-10-02 Thread
I can also confirm this issue also happens to me, and that downgrading glibmm from 2.66.1-1 to 2.64.2-2 successfully resolves the issue. I followed similar debugging steps as r...@thoryk.com above which produced the same backtrace, before finding this bug already reported. What I can add is from