This looks like an old report, but I ran into the same type of issue.
I do not have a solution, but an ugly hack to test if zenity is running
and if not kill the children processes.
That statement just looks wrong o.O
At any rate ...
Take a command foo ...
foo | zenity --progress --auto-kill &
This looks like an old report, but I ran into the same type of issue.
I do not have a solution, but an ugly hack to test if zenity is running
and if not kill the children processes.
That statement just looks wrong o.O
At any rate ...
Take a command foo ...
foo | zenity --progress --auto-kill &
This looks like an old report, but I ran into the same type of issue.
I do not have a solution, but an ugly hack to test if zenity is running
and if not kill the children processes.
That statement just looks wrong o.O
At any rate ...
Take a command foo ...
foo | zenity --progress --auto-kill &
This looks like an old report, but I ran into the same type of issue.
I do not have a solution, but an ugly hack to test if zenity is running
and if not kill the children processes.
That statement just looks wrong o.O
At any rate ...
Take a command foo ...
foo | zenity --progress --auto-kill &
This looks like an old report, but I ran into the same type of issue.
I do not have a solution, but an ugly hack to test if zenity is running
and if not kill the children processes.
That statement just looks wrong o.O
At any rate ...
Take a command foo ...
foo | zenity --progress --auto-kill &
This looks like an old report, but I ran into the same type of issue.
I do not have a solution, but an ugly hack to test if zenity is running
and if not kill the children processes.
That statement just looks wrong o.O
At any rate ...
Take a command foo ...
foo | zenity --progress --auto-kill &
