You are not logged in.
Hello,
After jack update the other day:
[2019-08-20 XX:XX] [ALPM] removed jack2-dbus (1.9.12-9)
[2019-08-20 XX:XX] [ALPM] installed jack2 (1.9.12-10)
My logs are now flooded with messages like these:
pulseaudio[XXXXX]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
pulseaudio[XXXXX]: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
pulseaudio[XXXXX]: JackEngine::XRun: client = PulseAudio JACK Sink was not finished, state = Triggered
pulseaudio[XXXXX]: JackEngine::XRun: client = PulseAudio JACK Sink was not finished, state = Running
pulseaudio[XXXXX]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
pulseaudio[XXXXX]: JackEngine::XRun: client = PulseAudio JACK Sink was not finished, state = Running
pulseaudio[XXXXX]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Anyone knows what does it mean? Point me in the right direction to troubleshoot/debug.
Thanks
Last edited by jnbrains (2019-08-23 06:23:11)
Offline
[2019-08-20 XX:XX] [ALPM] removed jack2-dbus (1.9.12-9)
[2019-08-20 XX:XX] [ALPM] installed jack2 (1.9.12-10)
This might be because jack2-dbus has been replaced by jack2. Was this your intention on upgrade? Have you tried resorting back to jack2-dbus?
Offline
Yes, it seems that jack2 has replaced jack2-dbus.
Last night I've tried to update pulseaudio to [testing] to see if it's fix the issue - it did not.
Then I build jack2-dbus-git from AUR and no more annoying messages (fix/workaround).
It appears my current configuration is tailored narrowly towards the D-Bus implementation of jack2.
I will have to figure out if I can reconfigure it to work with jack2 as well.
Thanks "d_fajardo" for the reply.
Offline
You're welcome. I believe you can continue to use jack2 but you also need to install pulseaudio-jack which I've never tried. Using jack2-dbus is just more straightforward.
Offline