[LAU] could not start jack - already registered problem

Hartmut Noack zettberlin at linuxuse.de
Thu Apr 25 13:33:38 UTC 2013


Am 25.04.2013 13:27, schrieb Patrick Shirkey:
> 
> On Thu, April 25, 2013 8:14 pm, Hartmut Noack wrote:
>> Am 25.04.2013 09:56, schrieb Patrick Shirkey:
>>>
>>> On Thu, April 25, 2013 4:40 pm, Hartmut Noack wrote:
>>>> Am 24.04.2013 17:15, schrieb Johannes Kroll:
>>>>> On Wed, 24 Apr 2013 16:10:56 +0200
>>>>> Hartmut Noack <zettberlin at linuxuse.de> wrote:
>>>>>
>>>>>> Am 24.04.2013 15:51, schrieb Len Ovens:
>>>>>>>
>>>>>>> On Wed, April 24, 2013 6:26 am, Hartmut Noack wrote:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I run KXStudio on Ubuntu 12.10 on a Lenovo Ideapad with a MAudio
>>>>>>>> Mobile
>>>>>>>> Pre USB1 interface.
>>>>>>>>
>>>>>>>> Normaly all this works near perfection but there is a problem
>>>>>>>> starting
>>>>>>>> Jack:
>>>>>>>>
>>>>>>>
>>>>>>>> Tue Apr 23 09:58:52 2013: ERROR: cannot register object path
>>>>>>>> "/org/freedesktop/ReserveDevice1/Audio2": A handler is already
>>>>>>>> registered for /org/freedesktop/ReserveDevice1/Audio2
>>>>>>>> Tue Apr 23 09:58:52 2013: ERROR: Failed to acquire device name :
>>>>>>>> Audio2
>>>>>>>> error : A handler is already registered for
>>>>>>>> /org/freedesktop/ReserveDevice1/Audio2
>>>>>>>
>>>>>>> Ok, so what application already has the audio port? Are you running
>>>>>>> an
>>>>>>> audio or video player? Have you been using a web browser that was
>>>>>>> seeing a
>>>>>>> video or just hit a page with video adds?
>>>>>>>
>>>>>>> To put it another way, does this problem show up right after a fresh
>>>>>>> login?
>>>>>>
>>>>>> Exactly: after a fresh login.
>>>>>>
>>>>>>> or only after having used the system for a while. What does your
>>>>>>> desktop use for most of it's non-jack audio output?
>>>>>>
>>>>>> Before I do anything else, I check if Jack is running. Browser, Skype
>>>>>> and the like use Pulse Jack sink, so I let Cadence start pulse-jack
>>>>>> after starting Jack.
>>>>>
>>>>> The command "lsof /dev/snd/pcm*" should show a list of commands which
>>>>> are using any sound cards. Try it the next time the problem shows up.
>>>>
>>>> Right now I have go the situation:
>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>> zettberlin at zettberlin-Lenovo-U410:~$ lsof /dev/snd/pcm*
>>>> zettberlin at zettberlin-Lenovo-U410:~$ cat /proc/asound/cards
>>>>  0 [Loopback       ]: Loopback - Loopback
>>>>                       Loopback 1
>>>>  1 [PCH            ]: HDA-Intel - HDA Intel PCH
>>>>                       HDA Intel PCH at 0xeb610000 irq 46
>>>>  2 [MobilePre      ]: USB-Audio - MobilePre
>>>>                       M Audio MobilePre at usb-0000:00:14.0-2, full
>>>> speed
>>>>
>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>> Thu Apr 25 08:29:57 2013: JACK server starting in realtime mode with
>>>> priority 10
>>>> Thu Apr 25 08:29:57 2013: ERROR: cannot register object path
>>>> "/org/freedesktop/ReserveDevice1/Audio2": A handler is already
>>>> registered for /org/freedesktop/ReserveDevice1/Audio2
>>>> Thu Apr 25 08:29:57 2013: ERROR: Failed to acquire device name : Audio2
>>>> error : A handler is already registered for
>>>> /org/freedesktop/ReserveDevice1/Audio2
>>>> Thu Apr 25 08:29:57 2013: ERROR: Audio device hw:MobilePre,0 cannot be
>>>> acquired...
>>>> Thu Apr 25 08:29:57 2013: ERROR: Cannot initialize driver
>>>> Thu Apr 25 08:29:57 2013: ERROR: JackServer::Open failed with -1
>>>> Thu Apr 25 08:29:57 2013: ERROR: Failed to open server
>>>> Thu Apr 25 08:30:04 2013: ------------------
>>>> Thu Apr 25 08:30:04 2013: Controller activated. Version 1.9.9.5
>>>> (unknown) built on Sat Dec 22 19:50:40 2012
>>>> Thu Apr 25 08:30:04 2013: Loading settings from
>>>> "/home/zettberlin/.config/jack/conf.xml" using expat_2.1.0 ...
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'engine':'driver':'(null)'
>>>> to value "alsa"
>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>> 'engine':'realtime':'(null)'
>>>> to value "true"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'engine':'verbose':'(null)'
>>>> to value "false"
>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>> 'engine':'client-timeout':'(null)' to value "1000"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'device'
>>>> to
>>>> value "hw:2"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'capture'
>>>> to value "hw:MobilePre,0"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'playback'
>>>> to value "hw:MobilePre,0"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'rate' to
>>>> value "48000"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'period'
>>>> to
>>>> value "256"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'nperiods'
>>>> to value "3"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'hwmon' to
>>>> value "false"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'hwmeter'
>>>> to value "false"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'duplex'
>>>> to
>>>> value "true"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'softmode'
>>>> to value "true"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'monitor'
>>>> to value "false"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'dither'
>>>> to
>>>> value "n"
>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'shorts'
>>>> to
>>>> value "true"
>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>> 'drivers':'alsa':'midi-driver' to value "seq"
>>>> Thu Apr 25 08:30:04 2013: Listening for D-Bus messages
>>>> Thu Apr 25 08:30:04 2013: Starting jack server...
>>>> Thu Apr 25 08:30:04 2013: JACK server starting in realtime mode with
>>>> priority 10
>>>> Thu Apr 25 08:30:05 2013: Acquired audio card Audio2
>>>> Thu Apr 25 08:30:05 2013: creating alsa driver ...
>>>> hw:MobilePre,0|hw:MobilePre,0|256|3|48000|0|0|nomon|swmeter|soft-mode|16bit
>>>> Thu Apr 25 08:30:05 2013: Using ALSA driver USB-Audio running on card 2
>>>> - M Audio MobilePre at usb-0000:00:14.0-2, full speed
>>>> Thu Apr 25 08:30:05 2013: configuring for 48000Hz, period = 256 frames
>>>> (5.3 ms), buffer = 3 periods
>>>> Thu Apr 25 08:30:05 2013: ALSA: final selected sample format for
>>>> capture: 16bit little-endian
>>>> Thu Apr 25 08:30:05 2013: ALSA: use 3 periods for capture
>>>> Thu Apr 25 08:30:05 2013: ERROR: ALSA: cannot set hardware parameters
>>>> for capture
>>>> Thu Apr 25 08:30:05 2013: ERROR: ALSA: cannot configure capture channel
>>>> Thu Apr 25 08:30:05 2013: ERROR: Cannot initialize driver
>>>> Thu Apr 25 08:30:05 2013: ERROR: JackServer::Open failed with -1
>>>> Thu Apr 25 08:30:05 2013: ERROR: Failed to open server
>>>> ##############################################################
>>>> Now I unplug the Mobile Pre....
>>>> Replug it
>>>> And:
>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>> Thu Apr 25 08:34:19 2013: ------------------
>>>> Thu Apr 25 08:34:19 2013: Controller activated. Version 1.9.9.5
>>>> (unknown) built on Sat Dec 22 19:50:40 2012
>>>> Thu Apr 25 08:34:20 2013: Loading settings from
>>>> "/home/zettberlin/.config/jack/conf.xml" using expat_2.1.0 ...
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'engine':'driver':'(null)'
>>>> to value "alsa"
>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>> 'engine':'realtime':'(null)'
>>>> to value "true"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'engine':'verbose':'(null)'
>>>> to value "false"
>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>> 'engine':'client-timeout':'(null)' to value "1000"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'device'
>>>> to
>>>> value "hw:2"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'capture'
>>>> to value "hw:MobilePre,0"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'playback'
>>>> to value "hw:MobilePre,0"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'rate' to
>>>> value "48000"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'period'
>>>> to
>>>> value "256"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'nperiods'
>>>> to value "3"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'hwmon' to
>>>> value "false"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'hwmeter'
>>>> to value "false"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'duplex'
>>>> to
>>>> value "true"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'softmode'
>>>> to value "true"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'monitor'
>>>> to value "false"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'dither'
>>>> to
>>>> value "n"
>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'shorts'
>>>> to
>>>> value "true"
>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>> 'drivers':'alsa':'midi-driver' to value "seq"
>>>> Thu Apr 25 08:34:20 2013: Listening for D-Bus messages
>>>> Thu Apr 25 08:34:20 2013: Starting jack server...
>>>> Thu Apr 25 08:34:20 2013: JACK server starting in realtime mode with
>>>> priority 10
>>>> Thu Apr 25 08:34:20 2013: Acquired audio card Audio2
>>>> Thu Apr 25 08:34:20 2013: creating alsa driver ...
>>>> hw:MobilePre,0|hw:MobilePre,0|256|3|48000|0|0|nomon|swmeter|soft-mode|16bit
>>>> Thu Apr 25 08:34:20 2013: Using ALSA driver USB-Audio running on card 2
>>>> - M Audio MobilePre at usb-0000:00:14.0-2, full speed
>>>> Thu Apr 25 08:34:20 2013: configuring for 48000Hz, period = 256 frames
>>>> (5.3 ms), buffer = 3 periods
>>>> Thu Apr 25 08:34:20 2013: ALSA: final selected sample format for
>>>> capture: 16bit little-endian
>>>> Thu Apr 25 08:34:20 2013: ALSA: use 3 periods for capture
>>>> Thu Apr 25 08:34:20 2013: ALSA: final selected sample format for
>>>> playback: 16bit little-endian
>>>> Thu Apr 25 08:34:20 2013: ALSA: use 3 periods for playback
>>>> Thu Apr 25 08:34:20 2013: port created: Midi-Through:midi/playback_1
>>>> Thu Apr 25 08:34:20 2013: port created: Midi-Through:midi/capture_1
>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:capture_1'
>>>> Thu Apr 25 08:34:20 2013: New client 'system' with PID 0
>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:capture_2'
>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:playback_1'
>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:playback_2'
>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port
>>>> 'system:midi_capture_1'
>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port
>>>> 'system:midi_playback_1'
>>>> ################################################################
>>>>
>>>> Please, people! Is there nobody out there who could say, what is
>>>> registering the Device? I guess, it has to do with dbus but I really
>>>> would like to jump straight to the core of the problem, learning all
>>>> mysteries of dbus/freedesktop/Jackdbus whatever is not an option for
>>>> me.
>>>> So if anybody could point me to that spurious registering-process it
>>>> would be most appreciated :-)
>>>>
>>>
>>>
>>> You might have better luck with this one on the PA mailing list.
>>
>> So you suspect PA (and not dbus) to be the registering spectre?
>>
>> If I remember correctly I have tried some PA-voodoo also. Such as
>> killall -9 pulseaudio. But to no avail.
>>
>> Anyway thanks for the hint: I will try once more to find out, whether PA
>> has the custom to "register" handlers for
>> /org/freedesktop/ReserveDevice1/Audio2
>>
> 
> 
> You can try adding
> 
>   autospawn = no

This is in the file already, guess KXStudio does it automagically. And
it looks like it works, PA never starts automatically and it does not
respawn as I kill it.

In fact I do not believe, that the problem is directly related to pulse...

> 
> to
> 
>    ~/.pulse/client.conf
> 
> 
> This is reminiscent of the other pulse bug.
> 
> 
> 
> --
> Patrick Shirkey
> Boost Hardware Ltd
> 
> 



More information about the Linux-audio-user mailing list