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

Simon Wenner simon.wenner at gmail.com
Mon Oct 24 18:35:26 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 24.10.2011 06:58, schrieb Adrian Knoth:
> 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
>
$ jackd -d dummy
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2011 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10

$ jack_lsp
system:capture_1
system:capture_2
system:playback_1
system:playback_2

seems to work.
> Does it work? If so:
>
> $ alsa_out
>
> Should still be running.
>
Yes, It does not crash jackd.
>> 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.
>
I have no input devices attached. Not even a microphone. I think I
don't have a digital input... it's a cheap on-board audio chip.
>> ~$ 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.
>
I don't use the audio chip on my video card. Until recently I didn't
even know it exists. :-)

There is no pulseaudio on my system(s), as it creates an even bigger
nightmare in my audio landscape. In addition, I don't use Adobe Flash
(It used to block my sound device).

> You can sort this out:
>
> $ cat /proc/asound/cards
>
$ cat /proc/asound/cards
 0 [SB             ]: HDA-Intel - HDA ATI SB
                      HDA ATI SB at 0xfbdf4000 irq 16
 1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfbeec000 irq 44

0 is my preferred device.

> 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.
>
jackd -d alsa -d hw:0

Jackd still aborts when I start Totem or other Jack clients.

$ totem
JackSocketClientChannel read fail

HDMI is even worse, see below:

$ jackd -d alsa -d hw:1
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2011 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
control device hw:1
control device hw:1
audio_reservation_init
Acquire audio card Audio1
creating alsa driver ... hw:1|hw:1|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
Cannot initialize driver
JackServer::Open() failed with -1
Failed to open server

>
> HTH, and please report back your findings.

Thank you for your help. Audio on Linux is a nightmare and for the
average user it's just broken beyond repair. Anyway, in my opinion,
even if it is caused by my hardware, Jackd should never abort during
normal use.

Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOpa/nAAoJEMMF4eNtCPQVCdMQAMDQ8tLvQzXxrGtlIBehLJsd
gW80KIEqHwQjT2VcmdftWzEw2uboUOIDZ5l8HjCLnDmiGwMZ/ex/kCP5KTTfVdsn
kPHV4u3QoEzMjPJFU5qEAc8E9cvtrpRWAZvlQRDrun5V7M2I2um6w2nkLrc1Kpo7
KOjz+/8m1dc8dnpm4JSKEXety6JZE3kir+iGGp7TZI4IGIk8iaqdYhANXV4FBvV2
mYbqqlzCDYIt9QI1wl35avAKAzFkA2c8AedTl2h3nsOt/kbtcf+0V6ZyRQddk/dd
vbghtqYrJjLRBblhtLBg02mGKwzIzSwwa0AJVa+weJF4rjAUeJuPK71te4k6WbP1
jDYji9cICl7cXHD4IcNqxyktaQgeixza3nK28GrgBd7mg3yTAOhQ5zniolfSXx2+
0Pt1jYxLckcnR/UOWmxF26dPTYZpgibsmOasiRoUKxpGt8nzKEOjpSl2InKP/NGR
A3f623rZDlsNCYNd+0oImtwXaoNRlJfUIrd5/ZiYG+ghCBkwY5yMDWsrJ82zLdSi
iqiHDhDGtL41L9zB8i7x0IFcyh31iDwTsC9IDca/DNfQKf2uXiJmXp+rVS5mAqHO
zKUFg6Es7/0WDZ6eVyhyYK2jytd1b8xcS6keoL+c18RRP0nKInAaPTMn2VTK45jK
UFsre8in/g/ti7W1motb
=qjLW
-----END PGP SIGNATURE-----






More information about the pkg-multimedia-maintainers mailing list