Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I get the window below occasionally on shutdown. Is there any way to find out what the "Unknown" program is? Perhaps find the path of the executable?

enter image description here

share|improve this question
    
Related: Shutdown / restart does not complete –  8128 Sep 24 '11 at 13:48
1  
I'd look for any running(R) or zombie(Z) or other strange processes in the output of ps -eo pid,stat,args. –  arrange Sep 24 '11 at 15:13
    
I had this issue on every attempt to shut down or log out, and it turned out it was Kupfer which was causing it. Quitting Kupfer fixed this issue for me. –  Jon Apr 3 '13 at 21:29

3 Answers 3

This is actually a feature, not a bug. Before this, the system would log out at the loss of unsaved work and be blind to any damage.

Nowadays, applications that perform lengthy tasks worth awaiting, register themselves via DBus with the shell; these can be video encoding, uploading and syncing Ubuntu One or DropBox tasks and so on.

Sometimes applications may crash and therefore fail to deregister their pending tasks, and they may or may not be firefox.

You can investigate your shutdown inhibitor with any DBus viewer like d-feet:

On the session bus, the org.gnome.SessionManager interface will expose the method GetInhibitors(), which returns for example ['/org/gnome/SessionManager/Inhibitor2']. The object at this path will allow you to query various things, like GetAppId() (e.g. Handbrake), GetReason() (e.g. Encoding), GetToplevelXid() (e.g. 79691816L). Especially the latest may be of use: You could issue xwininfo -id 79691816 and thus verify if the window still exists and if it does, what its real title is.

share|improve this answer

Firefox has been suffering from a bad memory leak for a long time. And it has only gotten worse the last few releases (4, 5 & 6).

I often get this "Not responding" message and by trial & error have learned that it is coming from Firefox. To see if Firefox is causing this on your computer, consider trying the follow procedure:

when you get the Not Responding dialog, open System Monitor. Look for the firefox-bin executable in the Processes list and if you find it see if the Waiting Channel header says "futex_wait_queue_me": firefox-bin executable

If you see this entry, open a Terminal and type "killall firefox-bin". This commmand will terminate the process.

Now repeat whatever you did that created the Not Responding dialog (e.g., trying to restart or shutdown the computer) and see if everything is copacetic. If everything's smooth and you don't get another Not Responding dialog, you can deduce that it was the Firefox memory leak causing it.

share|improve this answer

Try running the grub update:

sudo update-grub

I had the same problem described above and this fixed it for me.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.