I am reopening this, since it has not been fixed in the application itself.
I consider this a major flaw in zenity as there seems to be no proper way (I'm trying for hours) to work around this.
bodhi.zazen's workaround is – I'm sorry to say – actually pretty bad, since it consumes CPU for no reason at all with that loop.
Additionally killing EVERY instant of the respective process can not be considered a sensible solution.
What if the user has other instances running? Take wget for example: killing wget completely will terminate all downloads the user may have already running.
I am reopening this, since it has not been fixed in the application itself.
I consider this a major flaw in zenity as there seems to be no proper way (I'm trying for hours) to work around this.
bodhi.zazen's workaround is – I'm sorry to say – actually pretty bad, since it consumes CPU for no reason at all with that loop.
Additionally killing EVERY instant of the respective process can not be considered a sensible solution.
What if the user has other instances running? Take wget for example: killing wget completely will terminate all downloads the user may have already running.