Hi, When I run QjackCtl with the --start parameter to automatically start JACK, this also ticks the corresponding checkbox in the setup dialog. The settings are then saved automatically, and the next time I run QjackCtl without --start, JACK will be started either way. I need to manually open the setup dialog and uncheck the autostart option again. Is this the a bug? I basically want only the command line to determine whether JACK is started or not. Another problem is that when I issue a shutdown from the desktop environment (Gnome), QjackCtl prevents the system from actually shutting down. It is minimized to the systray, but it does not close. On some systems, Gnome will also pop up a dialog box saying something along the lines of "the following application is preventing the system from shutting down...". I then need to close Qjackctl manually, or issue another shutdown command while it is minimized so my system will finally shut down. What's going on here? Why is QjackCtl questioning my decision to shut down the system? This only happens if the systray icon is enabled.

a. qjackctl --start command line option is persistent indeed. it has been like that for so long since i can't remember why i made it--well, no one complained, until now :)

b. qjackctl kindly refuses to shutdown forcedly if jackd is still running and clients are connected--to me thats a good reason but i believe you could get away if you turn off this setup/misc/confirm application close option.

On Mon, Feb 28, 2011 at 11:27:37PM +0100, Dominic Sacré wrote: Qjackctl generally is more 'persistent' that you'd expect. That's how it is :-) Your example shows that's is going a bit over the top: the whole point of command line options is to override any stored configuration, not to define it. Rui, I'm having other problems with all recent versions: * sometimes qjackctl removes connections right after they have been made, * and sometimes it makes some of its own, and refuses to disconnect them. Seems that the actual connection state and qjackctl's idea of it get out of sync. The only remedy if that happens is to terminate and restart it.

Hmm, ok... But I don't really care about QjackCtl being minimized, all I want is for my laptop to power down. How does QjackCtl prevent the system from shutting down anyway? If it weren't for QjackCtl, I wouldn't even know that an application has the power to do this.

On 03/03/2011 10:56 PM, Fons Adriaensen wrote: finally, as of todays svn trunk (qjackctl 0.3.7.10) commit-log: - Desktop environment session shutdown (eg. logout) is now tapped for graceful application exit, even though the main window is active (visible) and minimizing to system tray is enabled. Both were causing first shutdown/logout attempt to abort. Not anymore, hopefully ;).