LinuxQuestions.org - What Application/Daemon is responsible for opening ...

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - What Application/Daemon is responsible for opening ... (https://www.linuxquestions.org/questions/linux-general-1/what-application-daemon-is-responsible-for-opening-935005/)

What Application/Daemon is responsible for opening ...

a GUI dialog window to end a user launched Application that will not kill it's self?

I have another question as why is it when I post with Mageia LQ does not have an specific symbol for it to indicate which O.S I'm using.

Thanks in advance!

You are seeing such a dialog (in which case it would be helpful to know its title and the text in it)?

Or you want to create such a dialog (in which case do you mean "How can I display a GUI dialog window which can be used to kill a user launched Application?").

Thanks for the Reply!

When A GUI Application will not close, a dialog window opens that reads something like "This Program is not responding would you like to force-ably close it or continue to wait yes or no". I assume it is part of the Window Manager because if you click the mouse repeatably on a non responsive window,it appears.

Thanks for the clarification. Not an area I have expertise in. Which window manager are you using?

Thanks for the Reply!

Current Window Manager is xfwm4. All of the Distros I have used have this feature as well.

Netsearch results (here) suggested Xfce's xfwm4 has this capability since 4.6.0 but I could not find anything about whether it is enabled by default or how to configure it if not.

Most relevant pages:

Neither did I find anything by:

Reviewing the GUI configuration windows.
Inspecting the xfwm4 config files (.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml and ./.config/xfce4/xfwm4).
man -k <a variety of strings>

Thanks for the help!

I did not try to search this myself because most GUI issues are not documented all that well.

Thanks again! :hattip:

The WM is the program that dispatches messages (like mouse events, keyboard events, close events, ...) to the windows they belong to. That means that the WM is the program that actually recognizes if a window is not responsive and determines which action to start.
I don't know about xfwm4, but I use wmii and that WM allows me to configure which message to display and what action to start when a window is not responsive. I use Python to customize the WM, in my configuration file it looks like this (if this is helpful for anyone here):

Code:

def unresponsive_client(client):

    msg = 'The following client is not responding. What would you like to do?'

    resp = call('wihack', '-transient', client.id,

                'xmessage', '-nearmouse', '-buttons', 'Kill,Wait', '-print',

                '%s\n  %s' % (msg, client.label))

    if resp == 'Kill':

        client.slay()

This function is called from the WM if it detects a window that is not answering. Basically it does nothing more than displaying a message and asking if the user wants to wait for an answer or to kill the window.