Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Pro-Audio and qjackctl problem
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
Holysword
l33t
l33t


Joined: 19 Nov 2006
Posts: 807
Location: Greece

PostPosted: Thu Sep 27, 2012 8:06 pm    Post subject: [SOLVED] Pro-Audio and qjackctl problem Reply with quote

Hi there,
I am having problems to use pro-audio ebuilds for both jack-audio-connection-kit and qjackctl.

After installing media-sound/jack-audio-connection-kit-1.9.8 and media-sound/qjackctl-9999 I cannot start jack via qjackctl with the following error message:
Code:
21:56:43.914 Patchbay deactivated.
21:56:43.916 Statistics reset.
21:56:43.918 ALSA connection change.
21:56:43.928 JACK is starting...
21:56:43.928 /usr/bin/jackdbus -v -u -dalsa -dhw:0 -r48000 -p1024 -n3
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
jackdbus should be auto-executed by D-Bus message bus daemon.
If you want to run it manually anyway, specify "auto" as only parameter
21:56:43.938 ALSA connection graph change.
21:56:43.965 JACK was started with PID=21848.
21:56:43.967 JACK was stopped successfully.
21:56:43.968 Post-shutdown script...
21:56:43.968 killall jackdbus
jackdbus: no process found
21:56:44.374 Post-shutdown script terminated with exit status=256.
21:56:46.138 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started


I tried emerging media-sound/jack-audio-connection-kit-2.999 instead but it fails with the following error:
Code:
 * Package:    media-sound/jack-audio-connection-kit-2.9999
 * Repository: proaudio
 * Maintainer: proaudio@tuxfamily.org
 * USE:        alsa amd64 consolekit dbus elibc_glibc kernel_linux multilib pam policykit userland_GNU
 * FEATURES:   preserve-libs sandbox




>>> Unpacking source...
GIT update -->
   repository:               git://github.com/jackaudio/jack2.git
   at the commit:            b4349a570f9c366ea70eef60eff86d064228c164
   branch:                   master
   storage directory:        "/usr/portage/distfiles/egit-src/jack2.git"
   checkout type:            bare repository
Cloning into '/var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/work/jack-audio-connection-kit-2.9999'...
done.
Branch branch-master set up to track remote branch master from origin.
Switched to a new branch 'branch-master'
>>> Unpacked to /var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/work/jack-audio-connection-kit-2.9999
>>> Source unpacked in /var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/work


>>> Preparing source in /var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/work/jack-audio-connection-kit-2.9999 ...
 * Applying jack-audio-connection-kit-2.9999-link-fix.patch ...

 * Failed Patch: jack-audio-connection-kit-2.9999-link-fix.patch !
 *  ( /var/lib/layman/pro-audio/media-sound/jack-audio-connection-kit/files/jack-audio-connection-kit-2.9999-link-fix.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/temp/jack-audio-connection-kit-2.9999-link-fix.patch.out

 * ERROR: media-sound/jack-audio-connection-kit-2.9999 failed (prepare phase):
 *   Failed Patch: jack-audio-connection-kit-2.9999-link-fix.patch!
 *
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 2608:  Called epatch '/var/lib/layman/pro-audio/media-sound/jack-audio-connection-kit/files/jack-audio-connection-kit-2.9999-link-fix.patch'
 *   environment, line 1100:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of `emerge --info '=media-sound/jack-audio-connection-kit-2.9999'`,
 * the complete build log and the output of `emerge -pqv '=media-sound/jack-audio-connection-kit-2.9999'`.
 * This ebuild is from an overlay named 'proaudio': '/var/lib/layman/pro-audio/'
 * The complete build log is located at '/var/log/portage/media-sound:jack-audio-connection-kit-2.9999:20120927-195059.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/temp/environment'.
 * Working directory: '/var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/work/jack-audio-connection-kit-2.9999'
 * S: '/var/tmp/portage/media-sound/jack-audio-connection-kit-2.9999/work/jack-audio-connection-kit-2.9999'

_________________
"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)
Who will save us from pulseaudio and systemd?


Last edited by Holysword on Thu Jul 18, 2013 11:35 pm; edited 1 time in total
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Thu Sep 27, 2012 8:33 pm    Post subject: Re: Pro-Audio and qjackctl problem Reply with quote

Holysword wrote:

Code:

21:56:43.928 /usr/bin/jackdbus -v -u -dalsa -dhw:0 -r48000 -p1024 -n3
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started

OK, I know nor the jack2 nor the version of qjackctl you are running... so... perhaps... I'd better not help you... :twisted:

Nevermind ! :wink: From what I know from Jack 1 and a lower qjackctl, enabling the dbus interface is an option you can toggle under the Misc tab of qjackctk setup.
If it is the same for you then retry after unsetting ths option.
_________________
Back to top
View user's profile Send private message
Holysword
l33t
l33t


Joined: 19 Nov 2006
Posts: 807
Location: Greece

PostPosted: Thu Sep 27, 2012 8:42 pm    Post subject: Re: Pro-Audio and qjackctl problem Reply with quote

aCOSwt wrote:
OK, I know nor the jack2 nor the version of qjackctl you are running... so... perhaps... I'd better not help you... :twisted:

Nevermind ! :wink: From what I know from Jack 1 and a lower qjackctl, enabling the dbus interface is an option you can toggle under the Misc tab of qjackctk setup.
If it is the same for you then retry after unsetting ths option.

Thank you very much for your reply!
Indeed there is such an option. Except that I am using jack with dbus flag... so I decided to ENABLE the option instead...
This gave me a different bug though:

Code:
22:38:06.584 Patchbay deactivated.
22:38:06.588 Statistics reset.
22:38:06.590 ALSA connection change.
22:38:06.596 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
22:38:06.655 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
22:38:06.668 ALSA connection graph change.
Thu Sep 27 22:38:06 2012: Starting jack server...
Thu Sep 27 22:38:06 2012: Jack: server `default' registered
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::InitConnections size = 6523136
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::InitClients
Thu Sep 27 22:38:06 2012: JACK server starting in realtime mode with priority 10
Thu Sep 27 22:38:06 2012: Jack: JackShmMem::new index = 0 attached = b6772000 size = 82246176
Thu Sep 27 22:38:06 2012: Jack: JackShmMem::new placement size = 13048352
Thu Sep 27 22:38:06 2012: ERROR: Cannot lock down 82246176 byte memory area (Cannot allocate memory)
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::InitConnections size = 6523136
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::InitClients
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::InitConnections size = 6523136
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::InitClients
Thu Sep 27 22:38:06 2012: Jack: JackShmMem::new index = 1 attached = bd5c6000 size = 1040
Thu Sep 27 22:38:06 2012: Jack: Succeeded in locking 1040 byte memory area
Thu Sep 27 22:38:06 2012: Jack: Create non RT thread
Thu Sep 27 22:38:06 2012: Jack: ThreadHandler: start
Thu Sep 27 22:38:06 2012: Jack: playback device hw:0
Thu Sep 27 22:38:06 2012: Jack: capture device hw:0
Thu Sep 27 22:38:06 2012: Jack: apparent rate = 48000
Thu Sep 27 22:38:06 2012: Jack: frames per period = 1024
Thu Sep 27 22:38:06 2012: Jack: capture device hw:0
Thu Sep 27 22:38:06 2012: Jack: playback device hw:0
Thu Sep 27 22:38:06 2012: Jack: JackDriver::Open capture_driver_name = hw:0
Thu Sep 27 22:38:06 2012: Jack: JackDriver::Open playback_driver_name = hw:0
Thu Sep 27 22:38:06 2012: Jack: Check protocol client = 8 server = 8
Thu Sep 27 22:38:06 2012: Jack: JackEngine::ClientInternalOpen: name = system
Thu Sep 27 22:38:06 2012: Jack: JackEngine::AllocateRefNum ref = 0
Thu Sep 27 22:38:06 2012: Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system val = 0
Thu Sep 27 22:38:06 2012: Jack: JackEngine::NotifyAddClient: name = system
Thu Sep 27 22:38:06 2012: Jack: JackGraphManager::SetBufferSize size = 1024
Thu Sep 27 22:38:06 2012: Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Thu Sep 27 22:38:06 2012: Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Thu Sep 27 22:38:06 2012: Jack: JackDriver::SetupDriverSync driver sem in flush mode
Thu Sep 27 22:38:06 2012: control device hw:0
Thu Sep 27 22:38:06 2012: control device hw:0
Thu Sep 27 22:38:06 2012: ERROR: Failed to acquire device name : Audio0 error : Cannot allocate memory
Thu Sep 27 22:38:06 2012: ERROR: Audio device hw:0 cannot be acquired...
Thu Sep 27 22:38:06 2012: Jack: ~JackDriver
Thu Sep 27 22:38:06 2012: ERROR: Cannot initialize driver
Thu Sep 27 22:38:06 2012: Jack: no message buffer overruns
Thu Sep 27 22:38:06 2012: Jack: JackPosixThread::Stop
Thu Sep 27 22:38:06 2012: Jack: ThreadHandler: exit
Thu Sep 27 22:38:06 2012: ERROR: JackServer::Open() failed with -1
Thu Sep 27 22:38:06 2012: Jack: Succeeded in unlocking 82246176 byte memory area
Thu Sep 27 22:38:06 2012: Jack: JackShmMem::delete size = 0 index = 0
Thu Sep 27 22:38:06 2012: Jack: ~JackDriver
Thu Sep 27 22:38:06 2012: Jack: Succeeded in unlocking 1040 byte memory area
Thu Sep 27 22:38:06 2012: Jack: JackShmMem::delete size = 0 index = 1
Thu Sep 27 22:38:06 2012: Jack: cleaning up shared memory
Thu Sep 27 22:38:06 2012: Jack: cleaning up files
Thu Sep 27 22:38:06 2012: Jack: unregistering server `default'
Thu Sep 27 22:38:06 2012: ERROR: Failed to open server
Thu Sep 27 22:38:08 2012: Saving settings to "/Holysword//.config/jack/conf.xml" ...
22:38:09.872 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started


Any idea on that now?
If not, which version of jack/qjackctl are you using, such that I can try with your configuration?
_________________
"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)
Who will save us from pulseaudio and systemd?
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Thu Sep 27, 2012 9:26 pm    Post subject: Re: Pro-Audio and qjackctl problem Reply with quote

Holysword wrote:

Any idea on that now?
If not, which version of jack/qjackctl are you using, such that I can try with your configuration?

8O Well... I am afraid I cannot get other ideas.
As for what I am running h24 troublefree : Good old jack1 form portage (0.121.3) and qjackctl 0.3.9 from portage as well.
I have never experienced the need for jack2 which sole advantage I would see over jack1 for me is to enable several concurrent instances of its daemon.
_________________
Back to top
View user's profile Send private message
Holysword
l33t
l33t


Joined: 19 Nov 2006
Posts: 807
Location: Greece

PostPosted: Fri Sep 28, 2012 9:16 am    Post subject: Re: Pro-Audio and qjackctl problem Reply with quote

aCOSwt wrote:
O Well... I am afraid I cannot get other ideas.
As for what I am running h24 troublefree : Good old jack1 form portage (0.121.3) and qjackctl 0.3.9 from portage as well.
I have never experienced the need for jack2 which sole advantage I would see over jack1 for me is to enable several concurrent instances of its daemon.

I was interested in jack2 because of the support to firewire (ieee1394 flag). Is there a way to have the same with jack1 without forcing me to patch my kernel or other complications?
_________________
"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)
Who will save us from pulseaudio and systemd?
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Fri Sep 28, 2012 9:54 am    Post subject: Re: Pro-Audio and qjackctl problem Reply with quote

Holysword wrote:
I was interested in jack2 because of the support to firewire (ieee1394 flag). Is there a way to have the same with jack1 without forcing me to patch my kernel or other complications?

I get no firewire device so I cannot tell from my own experience.
Friends of mine reliably use jack1 and firewire thanks to ffado
_________________
Back to top
View user's profile Send private message
Holysword
l33t
l33t


Joined: 19 Nov 2006
Posts: 807
Location: Greece

PostPosted: Fri Sep 28, 2012 7:59 pm    Post subject: Re: Pro-Audio and qjackctl problem Reply with quote

aCOSwt wrote:
I get no firewire device so I cannot tell from my own experience.
Friends of mine reliably use jack1 and firewire thanks to ffado

I know ffado but jack2 has a direct support for it via compilation option (don't know about jack1...) so I was supposing it would work better. Also some guys at the IRC channel were mentioning that things work pretty well with jack2.

Anyway, I figured out what was going on (even with jack-0.121 version). It was not being able to start jack because timidity and/or chrome and/or audacious apparentely are "taking" the hw:0 interface. I don't know why this is so, because I have another installation of Gentoo and jack is able to start even with all of these started. In fact it was showing timidity and audacious under ALSA tab in Connection.

Is that normal? Am I doing something wrong?
_________________
"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)
Who will save us from pulseaudio and systemd?


Last edited by Holysword on Fri Sep 28, 2012 8:04 pm; edited 1 time in total
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum