Package: ekiga Version: 2.0.3-6 When a user attempts to shut down ekiga through the window manager's "Close" function (conventionally mapped to Alt+F4), the window is killed but not the underlying process. If the user then attempts to start ekiga again, (s)he is told that another instance of ekiga is running. If the user instead logs out, the ekiga process starts spinning at 99% CPU usage. The runaway ekiga process responds normally to SIGTERM.
The same thing happens if the user logs out without explicitly exiting ekiga as described below. Exiting ekiga through the Call->Quit menu entry works normally. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
