18 May
2009
18 May
'09
12:24 p.m.
drew Roberts <zotz(a)100jamz.com> writes:
On Monday 18 May 2009 06:44:45 Nedko Arnaudov wrote:
Packaging not suited to user's needs. I explain it like this. Also
packagers are not given enough warnings about the problems. Both
problems are fixed in svn and thus in next jack2 release.
No, it is FUD campaign in lau ml :(
The official jack api is respected and it the JackNoStartServer option
IS respected.
OK, so how do we explain the behavior that Fons is seeing. No jack is running.
He starts qjackctl.
qjackctl shows a jack is running once it is started.
That means jack server is running. It may have been started through dbus
or through qjackctl (i think it has that option - autostart jack on
launch).
the jack that qjackctl finds started is not the one it
is configured to start.
The the server was started through dbus mechanism. This is caused by
mixing the two models. OTOH you dont get messages in qjackctl when jackd
is autolaunched by an application. Once again, package needs to be fixed
and there is fix in the svn that should make it harder for packagers to
do this error.
(Is this about right for the one problem you described
Fons?)
I'm still not completely sure what proble Fons has. Except ban dbus
statement.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>