Yes, i built it myself from the latest git. Here is the readout from gdb
after I add a mixer strip and rename it. When i saw libjack I realised
it must be to do with my version of JACK. I usually use JACK 1. I
understand you use JACK 2. I tried it with that and I have no such
issues with non-mixer crashing so it seems to be a JACK1 vs JACK2 issue.
Read out -
[non-mixer] Add mixer strip "Unnamed"
[Thread 0x7fffeca3c700 (LWP 12295) exited]
[Thread 0x7fffedb82700 (LWP 12292) exited]
[New Thread 0x7fffedb82700 (LWP 12296)]
[New Thread 0x7fffeca3c700 (LWP 12299)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeca3c700 (LWP 12299)]
0x00007ffff7bc6108 in jack_port_get_latency_range ()
from /usr/lib/x86_64-linux-gnu/libjack.so.0
(gdb)
I will add a note to the bug tracker for reference,
Conor
On 29/09/14 17:49, J. Liles wrote:
On Mon, Sep 29, 2014 at 2:37 AM, Conor Mc Cormack
<[email protected] <mailto:[email protected]>> wrote:
Hi,
I have played around with your non tools in the past and have
recently revisited them. I am having an issue with non-mixer
crashing when renaming tracks. This is from an up to date git
build (happens on both 32bit AVLinux and 64bit KXStudio). Here are
my observations -
Add a track in non-mixer
Rename track - non-mixer crashes
Restart non-mixer and add track
Add new track to a group and give it a name
Now rename the track name - non-mixer doesn't crash
I thought this might be a workaround but I have found that it can
be unpredictable too. It doesn't crash at first but it can
randomly crash non-mixer when adding a track to a group. It
doesn't appear to matter whether this is a new group or an
existing group.
Regards,
Conor
When you say git build, does that mean you got it from the distros, or
built it yourself?
I can't reproduce this, so I'm going to need a backtrace from you.
Instructions are here:
http://non.tuxfamily.org/wiki/BugReports
In this case it would probably be esiest for you to follow the 'core
dump' procedures.
Also, create an issue on github here:
https://github.com/original-male/non/issues?q=is%3Aopen
Looks like someone has the same problem (issue #140)...
Since it seems to have come up recently and I can't repoduce it, I
assume it's due to some library that's changed (it's been a long while
since I upgraded anything).
But a bracktrace is worth a thousand speculations.
