Re: [Jack-Devel] jackdmp 1.9.10 on debian/sid refuse to start with --unlock

PrevNext  Index
DateWed, 17 Jul 2013 17:18:47 +0200
From hermann meyer <[hidden] at web dot de>
ToStéphane Letz <[hidden] at grame dot fr>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToStéphane Letz Re: [Jack-Devel] jackdmp 1.9.10 on debian/sid refuse to start with --unlock
Follow-UpBrendan Jones Re: [Jack-Devel] jackdmp 1.9.10 on debian/sid refuse to start with --unlock
Follow-UpStéphane Letz Re: [Jack-Devel] jackdmp 1.9.10 on debian/sid refuse to start with --unlock
Am 17.07.2013 14:38, schrieb Stéphane Letz:
> AFAIR --unlock was never really implemented in jack2
>
> Stéphane


not a big deal for me, but I could imagine that it should lead to a 
couple of confusions in the next time.
There is the "unlock" option in the qjackctl settings widget, which, if 
checked, now leads to "can not connect to server".

greets
hermann
>
> Le 17 juil. 2013 à 13:45, hermann meyer <[hidden]> a écrit :
>> Hi
>>
>> I've just upgraded my debian/sid system, that include a jackdmp update to version 1.9.10 (from 1.9.8)
>> Usually I use the -u option --unlock, but now jackd refuse to start with that option enabled. It say's
>>   unknown option character
>>
>> I just wonder, is the -u --unlock commandline option removed from jackdmp 1.9.10?
>> If so, is there a special reason for that?
>> Or is it debian specific?
>> However, the -u option is still mention in the debian man page, so there is at least a bug somewhere which needs to be addressed and solved.
>>
>> greets
>> hermann
>>
>>
PrevNext  Index

1374074340.14973_0.ltw:2, <51E6B5D7.2040501 at web dot de>