Click on a GUI window and show its process ID and command used to run the process

xprop | awk '/PID/ {print $3}' | xargs ps h -o pid,cmd
This command is useful when you want to know what process is responsible for a certain GUI application and what command you need to issue to launch it in terminal.
Sample Output
jack@jack-pc$ xprop | awk '/PID/ {print $3}' | xargs ps -p
 8025 /usr/lib/firefox-3.0.13/firefox

These Might Interest You

  • This command will loop until the process no longer exists, calling closemainwindow() this is as if the user clicked the close window x in the upper right hand corner and gives the user an opportunity to save work in many applications like notepad and other things. The $'s are escaped for Cygwin, if you want to run the same command from the RUN box or cmd.exe shell then just unescape the $'s: powershell -Command "while ($true){Try{$process=Get-Process calc -ErrorAction Stop}Catch [Microsoft.PowerShell.Commands.ProcessCommandException]{break;}if ($process) {$whateva=$process.CloseMainWindow()}else {break;}Start-Sleep -m 500}" Show Sample Output


    0
    powershell -Command "while (\$true){Try{\$process=Get-Process firefox -ErrorAction Stop}Catch [Microsoft.PowerShell.Commands.ProcessCommandException]{break;}if (\$process) {\$whateva=\$process.CloseMainWindow()}else {break;}Start-Sleep -m 500}"
    adanisch · 2014-07-04 11:06:22 0
  • Kill -9 immediately kills the given process number. $$ is the process ID of the process you are in.


    -2
    kill -9 $$
    chanux · 2009-02-17 15:10:29 0
  • After executing this, click on a window you want to track X Window events in. Explaination: "xev will track events in the window with the following -id, which we get by greping window information obtained by xwininfo" Show Sample Output


    2
    xev -id `xwininfo | grep 'Window id' | awk '{print $4}'`
    ktoso · 2009-09-19 22:47:16 0
  • Using -f treats the process name as a pattern so you don't have to include the full path in the command. Thus 'pkill -f firefox' works, even with iceweasel.


    0
    pkill -f <process name>
    eikenberry · 2010-06-19 02:36:31 0

What Others Think

This has been really usefull, thanks.
aperson · 483 weeks and 2 days ago
Great command! But just for the sake of avoiding that corner situation when we have another part of "xprop" that has "PID" in it, I find it safer to do like that: xprop | awk '($1=="_NET_WM_PID(CARDINAL)") {print $3}' | xargs ps h -o pid,cmd
Patola · 458 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: