[SOLVED] Execute CLI argument on firefox shutdown

sycamorex · 01-06-2016, 06:19 PM

Quote:

Originally Posted by Steven_G

It didn't work.

Yeah, it's the only xfce4-terminal running but that didn't work either.

And your solution is not all that different from ones I've tried by throwing spaghetti at the wall based on stuff I've found on the web.

This is starting to tick me off b/c it doesn't make any sense. (Not you guys. I appreciate the help. But things are not working the way I understand they should be based on my reading and advice from those more experienced than myself.)

What exactly didn't work? Can you describe it in more detail?

Steven_G · 01-06-2016, 07:16 PM

Clarification: It didn't achieve the desired goal.

Code:

/home/user/folder/firefox
xfce4-terminal -e "bash -c 'bleachbit -c firefox.* chromium.history;$SHELL'"
PID_TERM=$(pidof xfce4-terminal)
Kill -TERM -P $PID_TERM

When launched with a menu short cut FF runs.

When FF is closed xfce4 terminal opens and I see the visible output of it running bleachbit.

This is the desired behaviour.

Then the terminal window stays open and nothing I do will close the stupid thing; including your suggestion.

This is not the desired behaviour. IE: it "didn't work". And I'll be danged if I can figure out why the friggin terminal window cannot be made to close from inside this script.

sycamorex · 01-06-2016, 07:29 PM

Quote:

Originally Posted by Steven_G

Clarification: It didn't achieve the desired goal.

Code:

/home/user/folder/firefox
xfce4-terminal -e "bash -c 'bleachbit -c firefox.* chromium.history;$SHELL'"
PID_TERM=$(pidof xfce4-terminal)
Kill -TERM -P $PID_TERM

When launched with a menu short cut FF runs.

When FF is closed xfce4 terminal opens and I see the visible output of it running bleachbit.

This is the desired behaviour.

Then the terminal window stays open and nothing I do will close the stupid thing; including your suggestion.

This is not the desired behaviour. IE: it "didn't work". And I'll be danged if I can figure out why the friggin terminal window cannot be made to close from inside this script.

I don't know what this bleachbit does but perhaps you should kill it first (the same way you do xfce4-terminal) and then kill the terminal?

Steven_G · 01-06-2016, 07:55 PM

Quote:

Originally Posted by sycamorex

I don't know what this bleachbit does but perhaps you should kill it first (the same way you do xfce4-terminal) and then kill the terminal?

Bleachbit is a cleaning tool with a GUI frontend and a CLI interface. In CLI it executes the argument then closes itself. When I run pstree from the terminal instance that refuses to close bleachbit is not in the tree.

If I query the pidof the terminal instance manually from inside the terminal and then manually kill that pid the terminal instance will close. But not matter what syntax / structure I try to get the window to close from inside the script it just won't close.

Can you recommend a debug tool that would be good for a use case like this so I can get a closer look at what's going on and see why the last two lines appear to be failing to execute b/c it's not throwing any errors in the terminal instance.

Steven_G · 01-06-2016, 08:24 PM

strace won't run it. It throws exec errors.

bash -x runs the script and is verbose about what is going on until it hits the last two lines, the ones that aren't executing, and then it just hangs indefinitely w/ no output?

Steven_G · 01-06-2016, 08:42 PM

Code:

/home/user/folder/firefox
xfce4-terminal -e "bash -c 'bleachbit -c firefox.* chromium.history;$SHELL'"
PID_TERM1=$(pidof bleachbit)
Kill -TERM -P $PID_TERM1
sleep 3
PID_TERM2=$(pidof xfce4-terminal)
Kill -TERM -P $PID_TERM2
exit

Also achieves the exact same result as above: Lines one and two execute and then nothing else happens.

pan64 · 01-07-2016, 01:58 AM

in that case I would suggest you to make another wrapper, so xfce4-terminal -e bash -c your_script and in your_script you will be able to kill all the related processes, so xfce4-terminal will be able to close.

Steven_G · 01-07-2016, 11:22 AM

I appreciate the help. I marked all posts as helpful and the thread as solved b/c my original question was answered and I learned quite a few things.

I'm in the middle of building a custom system and have a million more important things to do. For now I will live with having to close the window manually and come back to this when I have more time to figure out why it's not working the way it should.

Thanx.