Hi David, Am Sonntag, den 13. Januar 2019 um 21:29:02 Uhr (+0100) schrieb David Runge: > What exactly leads you to believe, that jack offers "a wrong lib"? > All of the pro-audio applications were actually compiled against jack > (as it's still the default). > Do you have logs to provide some more insight? This might be very > relevant for upstream. For whatever reason when jackd (with jack version 1) starts up, it says it can't lock shared memory because a link/file is missing in /dev/shm/jack-1000/default/... (which is true). Jack works but obviously the locked shared memory isn't working/used (as the lmms error also indicates). You can probably try this yourself by replacing jack2 with jack, tell it to use locked memory and start it up. The file layout with jack2 is different: There is no directory tree named /dev/shm/jack-1000/default/ anymore, but all files are created directly in /dev/shm/ called jack_default_1000_0, jack-1000-0, ... -- Orm
