ray wrote:Perhaps the script should be modified to remove the current icon before adding another?
damNageHack wrote:ray wrote:Perhaps the script should be modified to remove the current icon before adding another?
Better add only a new one if there is not already one
But I wonder how this could be solved due to the usage of zenity ... Maybe with some kind of a lock file. You would have to check in both cases for a running zenity process (that shows the icon).
But ... why are you using the update notifier if you are not interested in updates? You can also increase the interval to check for updates.
zenity --notification \
pgrep -f zenity.+salix || zenity --notification \
ray wrote:One way i can think of is to move the zenity notification icon to a seperate script, so we can track the pid and kill it before showing another.
damNageHack wrote:Maybe try something like the following. You should only have to change the linezenity --notification \
topgrep -f zenity.+salix && zenity --notification \
Although, I can not reproduce it here with Salix Live 13.1.1 LXDE. The icon shows up again only if I've clicked on it before, but there is never more than one icon. Maybe my work around helps anyways.
man pgrep wrote: pgrep looks through the currently running processes and lists the pro-
cess IDs which matches the selection criteria to stdout. All the cri-
teria have to match. For example,
-f The pattern is normally only matched against the process name.
When -f is set, the full command line is used.
ray wrote:The pgrep line you wrote wouldnt work if there's more than one instance of zenity around, would it?