Forums
Hi Rui,
This has been bugging me quite some time. I always leave qjackctl running, while only activating jackd when needed, and stopping it when done, as I'd guess most people do. But whenever I log out of my KDE session, qjackctl alerts me that it will keep running in the system tray, and literally cancels my KDE logout while qjackctl does exit completely (no sys tray either). Also, if I immediately restart qjackctl after this occurrence, it automagically restarts jackd, and it's not set up to do that...ever!
Is there anyway to stop this behavior?
Thanks,
Lexridge
Re: Is there anyway to "fix" this?
The nag on desktop logout is an old one and I've been trying to address the issue but there were always something else in priority. I'll look at it again, when time permits.
OTOH, starting jackd automagically when you try to run a second qjackctl instance is a feature and that's just working as designed :)
Cheers
2nd Instance?
Hi Rui,
I really cannot see the point of running two instances of qjackctl, but I don't believe I was attempting to run a second instance, as the first one appeared to have exited. However, when I get home I will try this again, and then check the process list to see if qjackctl is indeed still running, albeit invisibly, in the background somewhere.
[EDIT] This is not a show stopper by any means, and I can always just manually stop qjackctl before leaving KDE. I just occasionally forget that it's running and walk away from my system thinking it's shutting down, only to find in the morning it did not. DOH! ;)
Thanks again,
Lexridge
Add new comment