When I shutdown my computer with /sbin/shutdown, the computer shuts down. However, if I had any firefox windows open when I shutdown, then when I restart firefox, I get the "Firefox was not properly shutdown" message.

I am working on a shutdown script to close firefox before calling shutdown. I have tried killall -s $x firefox, where $x is HUP, INT, QUIT, and a few others, but firefox is shutdown improperly every time.

How can I simulate clicking on the "X" in the window's corner within a script?

Did you try TERM?

I have a similar shutdown script that I use, and if I recall correctly, I use wmctrl to send a 'close' message (not quite sure though - I'm currently at work so I'll have to check when I get home).

it is as somethingfoo said : the only way to quit properly a graphical application is by using a window manager message (to simulate click on the "X" in the window corner), i'm not familiar with it so i'll let someone else explain how to do

this is true for graphical applications, otherwise, in order to kill processes on a shutdown, the signal which seems appropriated is HUP (means ancestors of the process are quitting, process needs to quit, to avoid zombies)

if i remember well, when in the good runlevel, the INIT process sends to all remaining processes a TERM, then a KILL signal, so there wouldn't be a need to send theses signals before... unless you really need to have a process killed to do job with its results

hi.

one option is to turn off this firefox feature. its called "resume from crash".

in firefox address bar type:

about:config

and you will see a list, lots, of options.

goto "browser.sessionstore.resume_from_crash" double click it and the value turns from true to false.

now try !!

p.s. lots of "hidden" features can be played with here

Yes. That is the default signal for killall. I also tried explicitly specifying it, as well as others. I should have mentioned TERM in the list of signals I've tried. As KrahnacK said though, that one is sent automatically anyway.

Thanks. I suspected that the close button did more than just send a signal. I'll look into using wmctrl if I have this problem in the future.

Thanks. That's the best solution for me. I never used that feature anyway. Unless I experience any problems, I'll keep this feature disabled.