redshift keeps running after gtk-redshift has quit [PATCH]

[Wicher]

This concerns at least redshift 1.6 .

If I start redshift via redshift-gtk, and then quit redshift-gtk (by quitting the X server), there's an orphaned redshift process left. If I then start a new desktop session I actually have two of them running.

This patch makes sure that when redshift-gtk exits, the associated redshift instance is terminated as well.

[Wolter HV (wolterh)]

This patch should be merged to the trunk!

[Wicher (wicher)]

Here's an improved version of the patch.

[Wicher (wicher)]

Well it's all a bit useless, since the error that occurs when the X server dies appears to be handled within GTK, is that right?

This is what is printed on stderr:
"gtk-redshift: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0."

I can't catch it and I couldn't find anything in pygtk (which I'm unfamiliar with) to register an exception handler to.