28 Feb
2011
28 Feb
'11
11:29 p.m.
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.
Thanks,
Dominic
28 Feb
28 Feb
11:59 p.m.
On 02/28/2011 10:27 PM, Dominic Sacré wrote:
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.
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
1 Mar
1 Mar
12:37 a.m.
Hi Rui,
On Monday 28 February 2011 23:59:31 Rui Nuno Capela wrote:
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 :)
Do you think this could be changed, so --start would just temporarily
override the setting from the setup dialog? Or maybe at least add a
--nostart command line option?
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.
Nope, that's not the behaviour I'm seeing. "Confirm application close"
is off. "Confirm server shutdown" is off. JACK is not running, and there
are no JACK clients (obviously) or ALSA clients connected. And yet, when
I choose "Shut down" from the Gnome menu, QjackCtl is only minimized to
the systray, and the system keeps running as if nothing happened.
Cheers,
Dominic
3 Mar
3 Mar
3:01 p.m.
On 02/28/2011 11:36 PM, Dominic Sacré wrote:
oh, now i get it. problem is, qjackctl doesn't make a distinction
whether you're closing the main window by clicking on the window manager
decoration [x] button or your desktop environment is being shutdown or
logging off. when the system tray icon is enabled, closing the main
window will just get it minimized, if not already.
i guess this issue cannot be solved right away. it would, if one could
distinguish a normal window-close from a desktop-shutdown, but there's
none from plain qt4. if it makes you happier, it also applies to kde :)
anyway, if and when that happens, you can be sure that requesting
desktop-shutdown a second time will work (qjackctl main window will be
minimized by that time:)
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi Rui,
On Monday 28 February 2011 23:59:31 Rui Nuno Capela wrote:
solved on svn trunk (qjackctl 0.3.7.8): now the command line server
start option (--start) is now independent of the configuration setup
option (Setup/Misc/Start JACK audio server on application startup).
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 :)
Do you think this could be changed, so --start would just temporarily
override the setting from the setup dialog? Or maybe at least add a
--nostart command line option?
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.
Nope, that's not the behaviour I'm seeing. "Confirm application close"
is off. "Confirm server shutdown" is off. JACK is not running, and there
are no JACK clients (obviously) or ALSA clients connected. And yet, when
I choose "Shut down" from the Gnome menu, QjackCtl is only minimized to
the systray, and the system keeps running as if nothing happened.
11:19 p.m.
On Thursday 03 March 2011 15:01:18 Rui Nuno Capela wrote:
On 02/28/2011 11:36 PM, Dominic Sacré wrote:
Obrigado, works nicely!
Do you think this could be changed, so --start
would just
temporarily override the setting from the setup dialog? Or maybe
at least add a --nostart command line option?
solved on svn trunk (qjackctl 0.3.7.8): now the command line server
start option (--start) is now independent of the configuration setup
option (Setup/Misc/Start JACK audio server on application startup). oh, now i get it. problem is, qjackctl doesn't
make a distinction
whether you're closing the main window by clicking on the window
manager decoration [x] button or your desktop environment is being
shutdown or logging off. when the system tray icon is enabled,
closing the main window will just get it minimized, if not already.
i guess this issue cannot be solved right away. it would, if one
could distinguish a normal window-close from a desktop-shutdown, but
there's none from plain qt4. if it makes you happier, it also
applies to kde :)
anyway, if and when that happens, you can be sure that requesting
desktop-shutdown a second time will work (qjackctl main window will
be minimized by that time:)
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.
Actually, in the case of QjackCtl, the whole "close-button minimizes to
systray" behaviour never made much sense to me, mainly because it merely
minimizes the main window, but leaves other windows (connections, etc.)
open.
I like the systray icon because it allows me to quickly check JACK's
status while working in other applications (or while making music...).
Other than that, I think I'd prefer if QjackCtl and the window manager's
close-button always worked like they do when the systray icon is
disabled.
Cheers,
Dominic
11:56 p.m.
On Thu, Mar 03, 2011 at 11:19:16PM +0100, Dominic Sacré wrote:
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.
Clicking the 'close' icon will make the WM send a WM_DELETE_WINDOW
message. The application's reaction should be to close down, not
to minimise itself. Qjackctl's way to handle this seems to be
wrong. Window managers normally provide another icon and/or a
shortcut for minimise, and they normally don't even require the
app's support to perform this action.
Ciao,
--
FA
8 Mar
8 Mar
5:26 p.m.
On 03/03/2011 10:56 PM, Fons Adriaensen wrote:
On Thu, Mar 03, 2011 at 11:19:16PM +0100, Dominic
Sacré 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 ;).
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
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.
Clicking the 'close' icon will make the WM send a WM_DELETE_WINDOW
message. The application's reaction should be to close down, not
to minimise itself. Qjackctl's way to handle this seems to be
wrong. Window managers normally provide another icon and/or a
shortcut for minimise, and they normally don't even require the
app's support to perform this action.
16 Mar
16 Mar
11:49 p.m.
On Tuesday 08 March 2011 17:26:19 Rui Nuno Capela wrote:
On 03/03/2011 10:56 PM, Fons Adriaensen wrote:
Thanks a lot Rui. With both "Confirm application close" and "Confirm
server shutdown" disabled, QjackCtl no longer interferes with me
shutting down the machine. Interestingly, for a split second Gnome still
shows a dialog saying "This program is blocking log out", but then shuts
down anyway :)
Cheers,
Dominic
On Thu, Mar 03, 2011 at 11:19:16PM +0100, Dominic
Sacré 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 ;). 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.
Clicking the 'close' icon will make the WM send a WM_DELETE_WINDOW
message. The application's reaction should be to close down, not
to minimise itself. Qjackctl's way to handle this seems to be
wrong. Window managers normally provide another icon and/or a
shortcut for minimise, and they normally don't even require the
app's support to perform this action.
1 Mar
1 Mar
12:25 a.m.
On Mon, Feb 28, 2011 at 11:27:37PM +0100, Dominic Sacré wrote:
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.
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.
Ciao,
--
FA
3 Mar
3 Mar
5:35 p.m.
On 02/28/2011 11:25 PM, Fons Adriaensen wrote:
On Mon, Feb 28, 2011 at 11:27:37PM +0100, Dominic
Sacré wrote:
not quite as fixed... but now on svn trunk (qjackctl 0.3.7.8) pressing
the connections "refresh" buttons do actually rebuild completely the
client/port lists and liaisons. caveat emptor: as a minor side-effect it
also is something like the opposite of "expand all"...
at least, you don't have to terminate and restart it anymore. just press
"refresh" :)
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
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.
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.
5002
days inactive
5018
days old
linux-audio-user@lists.linuxaudio.org
9 comments
3 participants
participants (3)
-
Dominic Sacré -
Fons Adriaensen -
Rui Nuno Capela