[01:04] <OvenWerk1> zequence: I have been testing running jackdbus from session start and using it as a back end for pulse. The only problem I have had so far is that if jackdbus crashes and a smart jack program is open, it imediately starts jackd. This breaks everything.
[01:05] <OvenWerk1> I am not, at this point sugesting we use jackdbus this way, but would like to point out that this is a problem with the way jackd2 is packaged.
[01:07] <OvenWerk1> jackdbus should be a separate package. I would suggest it come with a script called jackd  ;)  that acts as a wrapper for jackdbus.
[01:10] <OvenWerk1> I think this is a bug. I will have to bug the debian package. This is one of the things that causes people problems as even if they start jack from qjackctl at login, if something crashes jack (yes I have found some things) then jackd gets started without the user knowing. This is just bad.
[07:32] <zequence> OvenWerk1: I have suggested to Debian multimedia maintainers to separate jackd from jackdbus, and make them conflict with each other. They didn't like that
[07:32] <zequence> Or, at least one person didn't like that
=== cyphermox__ is now known as cyphermox
=== cyphermox_ is now known as cyphermox