Jack Errror - what to do?

Hi guys,

I suddenly have the problem that the jack server is not working anymore. Two days ago, when I last worked on the project, everything was still running.

Here is the message:

09:00:32.386 Statistik zurückgesetzt.
09:00:32.391 ALSA-Verbindung geändert.
09:00:32.394 D-BUS: Dienst ist verfügbar (org.jackaudio.service aka jackdbus).
09:00:32.559 D-BUS: JACK-Server konnte nicht gestartet werden. Tut mir Leid
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
09:00:32.585 Schaubild der ALSA-Verbindungen geändert.
Sat Sep 2 09:00:32 2023: Starting jack server…
Sat Sep 2 09:00:32 2023: Jack: Server default' registered Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::InitConnections size = 19050752 Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::InitClients Sat Sep 2 09:00:32 2023: JACK server starting in realtime mode with priority 10 Sat Sep 2 09:00:32 2023: self-connect-mode is "Don't restrict self connect requests" Sat Sep 2 09:00:32 2023: Jack: JackShmMem::new index = 0 attached = 1c6f7000 size = 107341340 Sat Sep 2 09:00:32 2023: Jack: JackShmMem::new placement size = 38108700 Sat Sep 2 09:00:32 2023: Jack: Succeeded in locking 107341340 byte memory area Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::InitConnections size = 19050752 Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::InitClients Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::InitConnections size = 19050752 Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::InitClients Sat Sep 2 09:00:32 2023: Jack: JackShmMem::new index = 1 attached = 23e7f000 size = 1196 Sat Sep 2 09:00:32 2023: Jack: Succeeded in locking 1196 byte memory area Sat Sep 2 09:00:32 2023: Jack: JackPosixThread::StartImp : create non RT thread Sat Sep 2 09:00:32 2023: Jack: JackPosixThread::ThreadHandler : start Sat Sep 2 09:00:32 2023: Jack: playback device hw:O22 Sat Sep 2 09:00:32 2023: Jack: capture device hw:O22 Sat Sep 2 09:00:32 2023: Jack: capture device hw:O22 Sat Sep 2 09:00:32 2023: Jack: playback device hw:O22 Sat Sep 2 09:00:32 2023: Jack: apparent rate = 44100 Sat Sep 2 09:00:32 2023: Jack: frames per period = 2048 Sat Sep 2 09:00:32 2023: Jack: JackDriver::Open capture_driver_name = hw:O22 Sat Sep 2 09:00:32 2023: Jack: JackDriver::Open playback_driver_name = hw:O22 Sat Sep 2 09:00:32 2023: Jack: Check protocol client = 9 server = 9 Sat Sep 2 09:00:32 2023: Jack: JackEngine::ClientInternalOpen: name = system Sat Sep 2 09:00:32 2023: Jack: JackEngine::AllocateRefNum ref = 0 Sat Sep 2 09:00:32 2023: Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 Sat Sep 2 09:00:32 2023: Jack: JackEngine::NotifyAddClient: name = system Sat Sep 2 09:00:32 2023: Jack: JackGraphManager::SetBufferSize size = 2048 Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Sat Sep 2 09:00:32 2023: Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Sat Sep 2 09:00:32 2023: Jack: JackDriver::SetupDriverSync driver sem in flush mode Sat Sep 2 09:00:32 2023: ERROR: control open "hw:O22" (No such device) Sat Sep 2 09:00:32 2023: ERROR: control open "hw:O22" (No such device) Sat Sep 2 09:00:32 2023: creating alsa driver ... hw:O22|hw:O22|2048|4|44100|0|0|nomon|swmeter|-|32bit Sat Sep 2 09:00:32 2023: ERROR: control open "hw:O22" (No such device) Sat Sep 2 09:00:32 2023: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode Sat Sep 2 09:00:32 2023: Jack: JackDriver::Close Sat Sep 2 09:00:32 2023: Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 Sat Sep 2 09:00:32 2023: Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Sat Sep 2 09:00:32 2023: Jack: JackEngine::ClientInternalClose ref = 0 Sat Sep 2 09:00:32 2023: Jack: JackEngine::ClientCloseAux ref = 0 Sat Sep 2 09:00:32 2023: Jack: JackGraphManager::RemoveAllPorts ref = 0 Sat Sep 2 09:00:32 2023: ERROR: control open "hw:O22" (No such device) Sat Sep 2 09:00:32 2023: ERROR: control open "hw:O22" (No such device) Sat Sep 2 09:00:32 2023: Jack: ~JackDriver Sat Sep 2 09:00:32 2023: ERROR: Cannot initialize driver Sat Sep 2 09:00:32 2023: Jack: no message buffer overruns Sat Sep 2 09:00:32 2023: Jack: JackPosixThread::Stop Sat Sep 2 09:00:32 2023: Jack: JackPosixThread::ThreadHandler : exit Sat Sep 2 09:00:32 2023: ERROR: JackServer::Open failed with -1 Sat Sep 2 09:00:32 2023: Jack: Succeeded in unlocking 107341340 byte memory area Sat Sep 2 09:00:32 2023: Jack: JackShmMem::delete size = 0 index = 0 Sat Sep 2 09:00:32 2023: Jack: ~JackDriver Sat Sep 2 09:00:32 2023: Jack: Succeeded in unlocking 1196 byte memory area Sat Sep 2 09:00:32 2023: Jack: JackShmMem::delete size = 0 index = 1 Sat Sep 2 09:00:32 2023: Jack: Cleaning up shared memory Sat Sep 2 09:00:32 2023: Jack: Cleaning up files Sat Sep 2 09:00:32 2023: Jack: Unregistering server default’
Sat Sep 2 09:00:32 2023: ERROR: Failed to open server
Sat Sep 2 09:00:33 2023: Saving settings to “/home/ms/.config/jack/conf.xml” …
09:00:41.454 Keine Verbindungsaufnahme als Client zum JACK-Server möglich. - Gesamtbetrieb schlug fehl. - Verbindungsaufnahme zum Server gescheitert. Bitte sehen Sie im Meldungsfenster nach weiteren Informationen.
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Does anyone know what I can do? I’m standing there like “an ox in front of a mountain” (as they say in German).

Ich verstehe es nicht.
Kaum hatte ich die Nachricht hier geschrieben, da funktioniert es wieder. Nichts verändert. Einfach nur (wie vorher auch mehrere male), Jack neu gestartet.

Seltsam!

Hi,
Please refer to this article:

When you start jack, you are using a device number. Replace the device number with a device name. The device name provides consistent identification.

In other words:
replace
hw:O22
with
hw:DEVICE-NAME

Hope that helps.

Disableing pipewire resolved it for me. Google the command for your linux distro. Do not uninstall pipewire on Ubuntu. It will remove gnome along with it for some reason.

The device named O22 is not present, but is the device selected to use.
That looks like a short name, does it match part of the model name of the audio device you were using two days ago?
Either replace that device, or select a different device to use.