[LAU] Too much information :(

Will Godfrey willgodfrey at musically.me.uk
Fri Dec 30 18:29:40 UTC 2016


On Sun, 18 Dec 2016 15:46:34 +0000
Will Godfrey <willgodfrey at musically.me.uk> wrote:

> On Sun, 18 Dec 2016 22:38:31 +1100
> Roger <gurusonic at gmail.com> wrote:
> 
> > On 18/12/16 19:46, Will J Godfrey wrote:  
> > > All of this has happened since that latest fetch from debian testing :(
> > > Maybe I'm imagining things, but we seem to be getting a lot more breakages
> > > and general strange behaviour from debian these days.
> > >    
> > Debian Stretch is in freeze transition preparing for next release. Soft 
> > freeze happens on 5 Jan so many packages may be pushed to beat this 
> > deadline causing testing to be at a fragile stage currently.
> > 
> > https://www.debian.org/News/weekly/2016/04/
> > 
> > Doesn't help fix your issue but may help explain why it happened.
> > 
> > Roger  
> 
> Didn't think of that  :(
> 
> Thanks, I can get round things for now.
> 

Hmmm, my normal state of mild confusion has now progressed to considerable
agitation!

As an experiment I tried using jackd1. Result, none of these messages. However
debian doesn't provide headers for this so I can't compile against it.

Go back to jackd2 (lot's of arsing about to do that) and once again I get a
continuous stream of messages even when there is nothing running except
qjackctl, so I'm wondering if the nice people at debian have inadvertently
compiled it with a debug switch enabled.

Is there such a switch, and can it be disabled without re-compiling.

I generally avoid compiling low-level stuff - I don't want to end up having to
also compile all the kit that's dependent on the debian installs.

Below is a few *seconds* worth from qjackctl's message window.

Jack: JackEngine::ClientNotify: no callback for notification = 4
Jack: JackEngine::ClientNotify: no callback for notification = 4
Jack: JackExternalClient::ClientNotify ref = 2 client = qjackctl name =
qjackctl notify = 4 Jack: JackSocketServerChannel::Execute : fPollTable i = 2
fd = 10 Jack: JackClient::ClientNotify ref = 2 name = qjackctl notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10


-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.


More information about the Linux-audio-user mailing list