Your message dated Thu, 03 Jun 2010 00:24:14 +0200
with message-id <87fx15rs35....@x4.delysid.org>
and subject line Re: Bug#583227: jackd: Clients spew debug output since jack2
transition
has caused the Debian Bug report #583227,
regarding jackd: Clients spew debug output since jack2 transition
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.)
--
583227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jackd
Version: 1.9.5~dfsg-13
Severity: important
SInce I upgraded to jack2 via apt-get, all of my JACK clients
seems to spew totally useless debug information to stdout.
For a simple example, here is the output of jack_lsp:
Jack: JackClient::SetupDriverSync driver sem in flush mode
Jack: JackPosixSemaphore::Connect jack_sem.1000_default_lsp
Jack: Already connected name = lsp
Jack: Clock source : system clock via clock_gettime
Jack: JackLibClient::Open name = lsp refnum = 2
system:capture_1
system:capture_2
system:capture_3
system:capture_4
system:capture_5
system:capture_6
system:capture_7
system:capture_8
system:capture_9
system:capture_10
system:capture_11
system:capture_12
system:capture_13
system:capture_14
system:capture_15
system:capture_16
system:capture_17
system:capture_18
system:playback_1
system:playback_2
system:playback_3
system:playback_4
system:playback_5
system:playback_6
system:playback_7
system:playback_8
system:playback_9
system:playback_10
system:playback_11
system:playback_12
system:playback_13
system:playback_14
system:playback_15
system:playback_16
system:playback_17
system:playback_18
Jack: jack_client_close
Jack: JackClient::Close ref = 2
Jack: JackClient::Deactivate
Jack: JackSocketClientChannel::Stop
Jack: JackPosixThread::Kill
Jack: JackClientSocket::Close
Jack: JackClientSocket::Close
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_lsp
Jack: JackLibClient::~JackLibClient
Jack: JackShmReadWritePtr1::~JackShmReadWritePtr1 2
Jack: Succeeded in unlocking 111 byte memory area
Jack: JackLibGlobals Destroy 1da4050
Jack: ~JackLibGlobals
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_system
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_freewheel
Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_lsp
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: JackPosixSemaphore::Disconnect
Jack: no message buffer overruns
Jack: ThreadHandler: exit
Jack: JackPosixThread::Stop
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 1
Jack: Succeeded in unlocking 994 byte memory area
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 0
Jack: Succeeded in unlocking 82208666 byte memory area
Jack: jack_client_close res = 0
As you can see, there is debug output before and after
the list of available ports. Previously, jack_lsp would
only list the available ports to stdout.
I see similar behaviour with clients like mplayer -ao jack.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages jackd depends on:
ii coreutils 8.5-1 GNU core utilities
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii libasound2 1.0.22-2 shared library for ALSA applicatio
ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib
ii libcelt0-0 0.7.1-1 The CELT codec runtime library
ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst
ii libexpat1 2.0.1-7 XML parsing C library - runtime li
ii libgcc1 1:4.4.4-2 GCC support library
ii libjack0 1.9.5~dfsg-13 JACK Audio Connection Kit (librari
ii libncurses5 5.7+20100313-2 shared libraries for terminal hand
ii libreadline6 6.1-2 GNU readline and history libraries
ii libsamplerate0 0.1.7-3 Audio sample rate conversion libra
ii libsndfile1 1.0.21-2 Library for reading/writing audio
ii libstdc++6 4.4.4-2 The GNU Standard C++ Library v3
ii python 2.5.4-9 An interactive high-level object-o
Versions of packages jackd recommends:
ii jackd-firewire 1.9.5~dfsg-13 JACK Audio Connection Kit (FFADO a
ii libpam-modules 1.1.1-3 Pluggable Authentication Modules f
ii qjackctl 0.3.6-1 User interface for controlling the
Versions of packages jackd suggests:
ii jack-tools 0.0.2-7 various JACK tools: plumbing, play
pn libjackasyn0 <none> (no description available)
pn meterbridge <none> (no description available)
-- debconf information:
* jackd/tweak_rt_limits: true
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang/k...@db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>
--- End Message ---
--- Begin Message ---
Adrian Knoth <a...@drcomp.erfurt.thur.de> writes:
> On Wed, May 26, 2010 at 04:31:29PM +0200, Mario Lang wrote:
>
>> SInce I upgraded to jack2 via apt-get, all of my JACK clients
>> seems to spew totally useless debug information to stdout.
>
> Could it be that you're running jackd/qjackctl with verbose output?
Yes, indeed, I am (historically) running jackd with -v.
It appears the verbose flag is visible to clients in JACK2.
Thats OK, I can drop -v.
Sorry for the fuzz.
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang/k...@db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>
--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
