Probably Qjackctl is starting jackdbus, which is buggy somehow, you can turn it off in Qjackctl setup.
Practicaly you don't need Qjackctl to work with JACK. if you serch jack_* you will found bunch of commands to work with JACKč I sometimes use them, specially in bash scripts.
Anyhow, you can use "patchage" if you want GUI connecting.
jack_alias jack_freewheel jack_midisine jack_showtime
jack_bufsize jack_iodelay jack_monitor_client jack_simple_client
jack_capture jack_latent_client jack_multiple_metro jack_simple_session_client
jack_capture_gui jack_load jack_net_master jack_snapshot
jack_connect jack_lsp jack_net_slave jack_test
jack_control jack_meter jack_netsource jack_thru
jack_cpu jack_metro jack_rec jack_transport
jack_cpu_load jack_midi_dump jack_samplerate jack_unload
jack_disconnect jack_midi_latency_test jack_server_control jack_wait
jack_evmon jack_midiseq jack_session_notify jack_zombie
If I understad it correctly it works also with 44100 samplerate, right? That's good then, you can proceed further with radio applications.