Bug#646248: [jackd2] assertion fails when client connects

Adrian Knoth adi at drcomp.erfurt.thur.de
Mon Oct 24 04:58:32 UTC 2011


On 10/22/11 19:24, Simon Wenner wrote:

Hi!

> Jackd aborts because of a failed assertion as soon as a client tries
> to connect to it. (tested with totem, supercollider and pure-data)

This is clearly a local issue, I'm running the same software without
problems.

Question is why.

First, let's agree to never run jackd as root for the reminder of this
debugging session. Running jackd as root is discouraged, misleading and
will not help solving the problem. ;)

Ok,

  $ jackd -d dummy
  $ jack_lsp

Does it work? If so:

  $ alsa_out

Should still be running.

> JackProcessSync::LockedTimedWait error usec = 5000000 err = Connection
> timed out
> Driver is not running

This doesn't look too good. Seems your soundcard isn't making any
progress, that is, it does not advance the hw pointer. Maybe you have
an unconnected digital-in that consequently doesn't get any clock
information? Changing the record source with alsamixer would be the
solution.

> ~$ lspci | grep Audio
> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
> 01:00.1 Audio device: ATI Technologies Inc HD48x0 audio

Ah, I have a theory here. The second audio interface seems to be your
HDMI-capable video card. The onboard audio is occupied by pulseaudio,
and jackd tries to use the HDMI card.

You can sort this out:

  $ cat /proc/asound/cards

With the correct numbers at hand, you can force jackd to use the card
you want, maybe the first or the second:

  $ jackd -d alsa -d hw:1   <-- second card

The order depends on what's listed in /proc/asound/cards.


HTH, and please report back your findings.





More information about the pkg-multimedia-maintainers mailing list