[patch] task manager spews console spam when a launcher task is closed or launcher is removed.

[moonbeam]

The current awn-task.c code does not adequately determine if signals need to be disconnected from tasks.

The current check for whether a task needs to have signals disconnected, at minimum, does not identify all tasks that should have their signals disconnected.

This can be observed by:
  1) Adding a launcher ( a terminal is fine).
  2) Open some (terminal) windows.
  3) Close the windows. (there will probably be some console spam).
  4) Remove the launcher (there will probably be continuous console spam until awn is restarted).

See patch (against trunk - revno: 133) attached to comments:

[moonbeam (rcryderman)]

This is a replacement patch. Against rev 133 of trunk. Upon further testing it appears there may still be some issues with the signal handling. However, on further reflection, it also appears that awn_task_win_enter_out and awn_task_manager_remove_launcher do not serve any purpose in the current code. So the patch that follows excises them along with the issues that went along with them (console spam related to signals attached to something that was not a task).

[Andrew Starr-Bochicchio (andrewsomething)]

0.2.1 released