Your message dated Tue, 25 Oct 2011 08:21:22 +0200
with message-id <4ea65562.1090...@drcomp.erfurt.thur.de>
and subject line Re: Bug#646248: [jackd2] assertion fails when client connects
has caused the Debian Bug report #646248,
regarding [jackd2] assertion fails when client connects
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
646248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: jackd2
Version: 1.9.7~dfsg-1
Severity: grave
Jackd aborts because of a failed assertion as soon as a client tries
to connect to it. (tested with totem, supercollider and pure-data)
~$ jackd -d alsa
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:0
control device hw:0
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
JackProcessSync::LockedTimedWait error usec = 5000000 err = Connection
timed out
Driver is not running
Cannot create new client
jackd: ../common/JackGraphManager.cpp:45: void
Jack::JackGraphManager::AssertPort(jack_port_id_t): Assertion
`port_index < fPortMax' failed.
Aborted
When I run it as root, it does not abort, but the clients are still
unable to connect.
~$ totem
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
jack server is not running or cannot be started
~$ 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
- --- System information. ---
Architecture: amd64
Kernel: Linux 3.0.0-1-amd64
Debian Release: wheezy/sid
990 testing security.debian.org
990 testing mirror.switch.ch
500 unstable mirror.switch.ch
150 experimental mirror.switch.ch
- --- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOovxbAAoJEMMF4eNtCPQVdeMP/jcqOjihxRldo+hHqG0C3Thg
ZxqND8CVuD9RV67DD1h7CAVN0GtTgR1hpkUA8yGtlaORWOaVg+1Cmodlv9WhaJci
EWASdkq5lK9OrMIRWzAowu3FaxViMjdMcmp0OkI/n/JDuiNysoO//LlOKusqH+T3
ogy0IEGendTnIMw9lrobMNZnLPIMvS0SI8LjzBflz5OP2Pgd00jFb9PpxmcZYX9/
k5vu6taZ9uLVDHdZBeVwVPqBuK8+bXlJTTlHIjURB6BU9lo1v3aMS//YWAUUGnmU
s2QGV+mmBQzYGW46Se7KuwZaYML9gLfd1IrDx2ubepzQSYdLZqqzSnNYVUKtujtf
OS2cfHEVQ+uGEWxk1L7QHiCEQ2MRDE9XqDzpnBaViCBTK/7Qht+fOhAHnjQ/7+Ek
Gz/6C0ICWQOPB39RcpvzQGYsyZBH3eEC2DhNrBoYK3ZTUqxRVI18v5PrqazBinuB
7b72bTyZyIEHhlz2XAlNgtIAbtAx7XUnxNlQCTh8FItNn/L2Cm8HG/J2mXDjyNbD
A3MNSoPp5DLvaDcPNud6dJpx0hR7ca/R/dPhawZi+stBG7ODh9X1yYKs6+4+0zhY
VoEN/bGeT57ArvjVD//JJQOsG8zeLMUgDjfcvYl9PneyazPpKBWMcfPNMeh+jmdd
To/Lw/7aTkuknmXREoZl
=4cjX
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 10/24/11 20:35, Simon Wenner wrote:
> 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.
The chip itself (Intel HDA) probably has digital input, even if no
physical plugs are provided.
So what you need to do now:
$ alsamixer -c 0
Then press F4, move the cursor to some analogue input like "Mic" or
maybe Mix, but not "Digital", press space.
This would select an analogue input for capture.
Then, try again.
I guess there's also a (somewhat discouraged) workaround:
$ jackd -d alsa -P
to select "playback only".
> 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).
Well, that's exactly what pulseaudio is for: multiplexing your audio
device to multiple applications.
> Anyway, in my opinion, even if it is caused by my hardware, Jackd
> should never abort during normal use.
There is no way to avoid it: if you tell jackd to record audio (and
that's what you do at the moment) and jackd doesn't get any input from
alsa, it has to give up. One could argue that an assertion is not the
clean way to handle the situation, but the net result is always the
same: jackd has to terminate itself, because the user request cannot be
fulfilled.
The jack authors are pretty clear wrt ALSA: they expect the user to take
all the required steps to set up the audio card before calling jackd.
You need this level of control in studio, broadcasting or all other
professional environments, the jack layer doesn't mess with the
underlying settings, it's the user's responsibility.
If you only want to multiplex your soundcard to different applications,
then jackd is the wrong tool for you. Use pulseaudio instead.
HTH
--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
