Bug#935980: jackd2: Segfaults when qjackctl patchbay is activated

2019-08-31 Thread Bernhard Übelacker
Hello Chris, I added it to your report guessing that it might be the issue you observed. Now I see your setup is way more complex than my test. To reveal some more information about your issue, you could install the package systemd-coredump, then in the journal should a backtrace appear after a

Bug#935980: jackd2: Segfaults when qjackctl patchbay is activated

2019-08-30 Thread Christopher David Howie
On 8/28/2019 12:29 PM, Christopher David Howie wrote: > jackd segfaults whenever the qjackctl patchbay is activated with a > non-empty set of patches. It's not clear to me exactly why this > happens, but it happens every time. I have done some additional testing on this and wanted to share the

Bug#935980: jackd2: Segfaults when qjackctl patchbay is activated

2019-08-28 Thread Bernhard Übelacker
Dear Maintainer, I tried to reproduce the issue, but unfortunately I receive no segmentation fault, instead a floating point exception. (By using the button with the play symbol at the middle bottom.) This happens there because the divisor frame_rate is zero. For this issue I could not find an

Bug#935980: jackd2: Segfaults when qjackctl patchbay is activated

2019-08-28 Thread Christopher David Howie
Package: jackd2 Version: 1.9.12~dfsg-2 jackd segfaults whenever the qjackctl patchbay is activated with a non-empty set of patches. It's not clear to me exactly why this happens, but it happens every time. I run jackd like so: $ jackd -R -d net -a 192.168.3.3 Here is jackd's output: