17 Oct
2009
17 Oct
'09
1 p.m.
It seems when you quit from the system tray icon (right-click->Quit),
qjackctl fails to execute script that is supposed to run after shutdown
(set on the options tab in the settings). Perhaps some timeout is
missing in there?
BTW, quitting from the regular GUI seems to work fine.
Best wishes,
Ico
18 Oct
18 Oct
11:04 a.m.
Ivica Ico Bukvic wrote:
It seems when you quit from the system tray icon
(right-click->Quit),
qjackctl fails to execute script that is supposed to run after shutdown
(set on the options tab in the settings). Perhaps some timeout is
missing in there?
BTW, quitting from the regular GUI seems to work fine.
well, it is working here as advertised--one of us is missing something... :)
my qjackctl (0.3.5.3 on cvs head, btw) does run the post-shutdown script
either from main-gui quit button or from system tray's icon context
menu. it always does it synchronously, waiting for the script to
complete execution before stopping for good.
maybe you're spawning some child process(es) in the background from your
script that gets abruptly killed when parent qjackctl actually terminates ?
seeya
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
19 Oct
19 Oct
1:44 p.m.
Hmmm, it seems "killall jackd; <custom command>" sometimes fails to
execute
custom command. Not sure if killall jackd is leftover from a previous
version, but now that I've removed that part and just left my custom
command, everything seems to work ok (at least so far).
Do I still need killall jackd there?
Ico
-----Original Message-----
From: Rui Nuno Capela [mailto:rncbc@rncbc.org]
Sent: Sunday, October 18, 2009 9:08 AM
To: Ivica Ico Bukvic
Cc: lau(a)lists.linuxaudio.org
Subject: Re: bug in qjackctl 0.3.5
Ivica Ico Bukvic wrote:
:)
It seems when you quit from the system tray icon
(right-click->Quit),
qjackctl fails to execute script that is supposed to run after shutdown
(set on the options tab in the settings). Perhaps some timeout is
missing in there?
BTW, quitting from the regular GUI seems to work fine.
well, it is working here as advertised--one of us is missing something...
my qjackctl (0.3.5.3 on cvs head, btw) does run the post-shutdown script
either from main-gui quit button or from system tray's icon context
menu. it always does it synchronously, waiting for the script to
complete execution before stopping for good.
maybe you're spawning some child process(es) in the background from
your
script that gets abruptly killed when parent qjackctl actually terminates
?
seeya
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
5:54 p.m.
Actually,
I stand corrected. The thing still fails intermittently. The post-shutdown
script looks as follows:
"cpufreq-set -g ondemand"
(obviously without quotation marks)
This is on Ubuntu 9.04.
It appears removing killall jackd makes no difference, making this problem
either way intermittent in its nature but only if closing qjackctl through
the systray icon (on Gnome desktop).
Ico
20 Oct
20 Oct
6:12 a.m.
On Mon, 19 Oct 2009 15:54:47 -0400, "Ivica Ico Bukvic" wrote:
Actually,
I stand corrected. The thing still fails intermittently. The
post-shutdown
script looks as follows:
"cpufreq-set -g ondemand"
(obviously without quotation marks)
This is on Ubuntu 9.04.
It appears removing killall jackd makes no difference, making this
problem
either way intermittent in its nature but only if
closing qjackctl
through
the systray icon (on Gnome desktop).
what do you by "fail intermitenttently" ? does it get executed or not? to
pick up some evidences, try to put it in a simple shell script where
stdout/err gets logged, eg.
#/bin/bash
cpufreq-set -g ondemand > qjackctl_cpufreq.log 2>&1
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
7:33 p.m.
what do you by "fail intermitenttently" ?
does it get executed or not? to
pick up some evidences, try to put it in a simple shell script where
stdout/err gets logged, eg.
#/bin/bash
cpufreq-set -g ondemand > qjackctl_cpufreq.log 2>&1
By "intermittently" I mean that when exiting from qjackctl sometimes my cpu
governor does revert back to ondemand and sometimes does not. Executing
script cpufreq -g ondemand from shell does it every time, so the only
logical conclusion I could extrapolate from this is that something funny
happens at qjackctl shutdown. That said, you've made an excellent
suggestion, so let me do that and see what happens.
Thanks for the suggestion!
Will keep you posted.
Best wishes,
Ico
9:32 p.m.
Ivica Ico Bukvic wrote:
let the script be more elaborate:
#!/bin/bash
cpufreq-set -g ondemand
rc=$?
echo "`date` rc=$rc" >> qjackctl_cpufreq.log
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
#/bin/bash
cpufreq-set -g ondemand > qjackctl_cpufreq.log 2>&1
Unfortunately this particular app generates no output whatsoever so logging
it does absolutely nothing. Its help file also suggests there is no way to
produce a verbose version either.
Any other ideas?
Ico
11:19 p.m.
Well, lo and behold now that I've built a script including one that comments
on when the shutdown was initiated, I cannot reproduce the problem, yet I do
know it has happened in the past. Perhaps because this is a script and not
an individual command? Or, it could be that when the CPU is getting hogged
by other things and I shutdown qjackctl it somehow does not give enough time
to propagate (this is on an Atom netbook). Or, there is always the safe bet
that I am hallucinating and we leave it at that :-)
I will keep the script going to see what happens and will let you know.
Many thanks for all your help.
Best wishes,
Ico
-----Original Message-----
From: Rui Nuno Capela [mailto:rncbc@rncbc.org]
Sent: Tuesday, October 20, 2009 7:28 PM
To: Ivica Ico Bukvic
Cc: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] bug in qjackctl 0.3.5
Ivica Ico Bukvic wrote:
logging
> it does absolutely nothing. Its help file also suggests there is no way
to
#/bin/bash
cpufreq-set -g ondemand > qjackctl_cpufreq.log 2>&1
Unfortunately this particular app generates no output whatsoever so produce a
verbose version either.
Any other ideas?
Ico
let the script be more elaborate:
#!/bin/bash
cpufreq-set -g ondemand
rc=$?
echo "`date` rc=$rc" >> qjackctl_cpufreq.log
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org 
21 Oct
21 Oct
6:17 a.m.
Ivica Ico Bukvic wrote:
you could tail the syslog in another window while you're
starting/stopping jackd.
#/bin/bash
cpufreq-set -g ondemand > qjackctl_cpufreq.log 2>&1
Unfortunately this particular app generates no output whatsoever so logging
it does absolutely nothing. Its help file also suggests there is no way to
produce a verbose version either.
Any other ideas?
5558
days inactive
5562
days old
linux-audio-user@lists.linuxaudio.org
9 comments
3 participants
participants (3)
-
Ivica Ico Bukvic -
Jörn Nettingsmeier -
Rui Nuno Capela