Unable to connect to playback

[m4l3z]

Hello there,

Samplv1 0.8.0
When running with the terminal :

samplv1_jack 
SuspendRefNum error
JackClient::Execute error name = samplv1-01
Server is not running
Server is not running
Server is not running
Server is not running

Jack log :

Tue Jan 17 16:26:58 2017: New client 'samplv1-01' with PID 5414
Tue Jan 17 16:26:58 2017: port 'a2j:samplv1 [130] (playback): in' created
Tue Jan 17 16:26:58 2017: port 'samplv1-01:in_1' created
Tue Jan 17 16:26:58 2017: port 'samplv1-01:in_2' created
Tue Jan 17 16:26:58 2017: port 'samplv1-01:in' created
Tue Jan 17 16:26:58 2017: port 'samplv1-01:out_1' created
Tue Jan 17 16:26:58 2017: port 'samplv1-01:out_2' created
Tue Jan 17 16:28:05 2017: ERROR: Failed to find port 'samplv1:in_1' to destroy
Tue Jan 17 16:28:05 2017: ERROR: Failed to find port 'samplv1:in_2' to destroy
Tue Jan 17 16:28:05 2017: ERROR: Failed to find port 'samplv1:in' to destroy
Tue Jan 17 16:28:05 2017: ERROR: Failed to find port 'samplv1:out_1' to destroy
Tue Jan 17 16:28:05 2017: ERROR: Failed to find port 'samplv1:out_2' to destroy

I cannot connect samplv1 to the system playback in standalone. Seems to work in lv2 tho.

Cheers,

[m4l3z]

This still happens to me as of today but only when Qt creates a new file dialog. Maybe a threading issue ? It happens when I try to open a file dialog for presets, or for the new microtonal feature.
As soon as the file dialog appears, the ports disconnect, and samplv1 thinks jack is not running anymore, only rebooting it work.

Cheers,

[rncbc]

try whether turning off Help > Configure... > Options > Use desktop environment native dialogs makes any difference.

[m4l3z]

Nope this doesn't change anything.
It looks like the same issue as this one but the manips did not help. Tried to play with the MIDI setup and the environment native dialogs/widgets.
The save button does not trigger this bug. Only when a dialog window is created.

Cheers

[rncbc]

what is exactly your system/desktop environment? kde/plasma, gnome, xfce, unity, etc.? what is the display server back-end? is it plain standard x11, or is it wayland or mir ?

[m4l3z]

I'm on Linux Mint 18.1, no DE just i3. (yes I know)
I just tried with mate/marco and xfce/xfwm4 and the bug remains.
AFAIK plain standard x11.

Cheers

[rncbc]

then what about jack? what's the environment you have to run jack?

• is it jack1 or jack2 is it jackd (classic) or is it jackdbus?
• what do you use to launch the jack-server? is it qjackctl, cadence, jack_control?
• do you have pulseaudio working with jack?
• which jack-midi driver or bridge? is it "none", "seq" or "raw"? is it a2jmidid or is it jack1's "alsa_midi" ?

seeya

[m4l3z]

Based on my running processes it seems to be jackdbus with jackd2 installed.
I use cadence to start the jack-server. (Just tried with qjackctrl and jack_control, same)
Yes pulseaudio is working with jack. (Bug still appears without)
jack-midi driver was set on none. I tried the others. And it's a2jmidid.

When using alsa sequencer as jack-midi driver and opening a dialog window, all the audio ports die but the midi port is still visible in catia.

Cheers

[rncbc]

have you tried it all without starting a2jmidid ?
or not running jackdbus at all? eg. killall jackdbus; chmod a-x /path/to/jackdbus; and then run jackd from a terminal command line instead? or use qjackctl with jack d-bus support disabled (see qjackctl > Setup > Misc tab)
please check all the possibilities as you're my eyes and ears there (fyi. i personally despise jackdbus while often preferring jackd1 with native "alsa_midi" back-end which works a lot (a huge lot) better than arcane a2jmidid. (nb. jackd2 has no "alsa_midi" and its "seq" is way too broken to be mentioned here).

byee

[m4l3z]

Alright so I killed jackdbus and a2jmidid and chmod'd them, started jackd manually(also tried with qjackctl, no d-bus) and the bug was still there.

Here are the lines from jack during samplv1 life cycle.
jackd-samplv1.txt

Thanks for your setup recommendation I might give it a try !
I don't know why I have the intuition that using jackd1 instead of jackd2 might fix it. Could it be a function that is implemented a bit differently between the two versions of the lib ? Gonna try and report.

[m4l3z]

It works with jackd1 ! I put the same settings as my jackd2 setup. jackdbus + a2jmidid running. Dialog windows does not induce crash. :)
I'll look a bit more into whether staying in jackd1 is suitable for me. Thanks a lot for all the questions/guided investigation. I hope it helps narrowing the possibilities.
Might have something to do with that jack graph thing (l163-168 of jackd-samplv1.txt).

Cheers

[rncbc]

jackd2 used to have this (quite stupid imho) option to actively prevent client auto-connections--could it be that it's on on your case?

[m4l3z]

Self connect mode is set on "Don't restrict self connect request".
Also the "Use default environment dialogs" does not stay unchecked at next startup.

[m4l3z]

(I tried the other self connect options, no change)

[rncbc]

Also the "Use default environment dialogs" does not stay unchecked at next startup.

what? wait, that's suspicious... maybe it crashed before it committed to the conf file last time you tested;
please try next time to turn it off, then quit and then start again; verify the setting is as was you touched it before; then test as usual

byee

[m4l3z]

No, it refuses to keep the setting at restart.
I modified the conf file manually. No more bug with jackd2 (WOOOH).
So it seems like it won't write to the conf file.
It was a permission issue.. chmod'd the .conf and it works fine now.
Now why the .conf file has not been created with the correct permissions, I do not know.

I think we did it Rui !

[rncbc]

probably you have migrated across distros, machines, disks, which had slightly different uids but same usernames ?

glad you nailed it, thanks for your patience and efforts during all this ordeal

cheers.

[m4l3z]

Perhaps..
Thanks for your patience and efforts too !

cheers

[m4l3z]

I'm sorry after all these manips I forgot I was still with jackd1..
Retransitioned to jackd2 and the bug is still there. :/

cheers