Fedora :: Determine Which Process Belongs To Which Window In System Monitor?
Feb 26, 2011
I have Fedora Linux 13 64bit system. I use System Monitor to check which process is taking how much memory and cpu. Normally I have dozens of Chrome and Firefox windows open. The Processes tab shows which process is taking how much cpu/ram resources but I unfortunately there is no option like right click and make the window active that matches the PID (the one process that I have currently highlighted). Usually there is a chrome process taking up 30 or 40 percent of CPU while dozens other chrome processes taking much less cpu. I must determine which chrome window ( or any application which has multiple instances running) is taking that much CPU time. So can some one help me to solve this problem?
I have Fedora Linux 13 64bit system. I use System Monitor to check which process is taking how much memory and cpu. Normally I have dozens of Chrome and Firefox windows open. The Processes tab shows which process is taking how much cpu/ram resources but I unfortunately there is no option like right click and make the window active that matches the PID (the one process that I have currently highlighted). Usually there is a chrome process taking up 30 or 40 percent of CPU while dozens other chrome processes taking much less cpu. I must determine which chrome window ( or any application which has multiple instances running) is taking that much CPU time.
I'm writing a C++ application and need to work with process substitution in the Bash shell. I'm trying to find a way to validate the paths passed as arguments to my program, some of which point to FIFO files created by process substitution.
Is there a shell (or C++) way that I can check if the system creates these files in /dev/fd or if they are created somewhere else?
there's this process on my system monitor that opens and closes by itself it does not have a description or a name and makes my hard drive spin like hell
I have been using AWN for years, having a startup script to run multiple instances of AWN and position it on each monitor correctly. This has worked fine but today I decided to upgrade the version of AWN. The only problem now being that the new version doesn't support multiple instances of AWN to be open at once.The new version of AWN does have an 'Add dock' button but that's no good as my setup isn't Xinerama so each monitor is it's own workspace, meaning I can't position the dock far left, because far left is the edge of the current monitor.
The ideal solution here would to be able to run multiple instances, as I can force each instance to a monitor with DISPLAY=0:1 etc.If anybody has any ideas on how to have AWN on each of the 3 monitors then please let me know.
I am facing problem with the fresh installation of Fedora 11. (I have moved from Fedora 9). When I try to view videos on ..... or use the Cheese Webcam Booth, I get blurred lines on the screen and I am unable to see any video or pic.
Also I noticed that the when i go to System > Preferences>Display, it shows me UNKOWN MONIOR.
However, if I got to System>Administration>Display and enter the su password, it shows me correct monitor and the graphics driver.
I am not sure if my original is related to the Unknown Monitor.
I also tried to install Nvidia driver but it crashed the xserver and I had remove the driver.
My Monitor is LG 700E and Graphics card is from intel. as I am not able watch any video.
I am looking for a simple process monitor to monitor CPU, ram, swap usage of selected processes and log the information to a csv file at a specified interval.
Or is there a way pipe the information I want from top to a csv file?
I'd like to determine what process has ownership of a lock-file. The lock-files are simply a file with a specific name that has been created.So, how can I determine what process has a particular file open in Linux? Preferably a one-liner type or a particular Linux tool solution would be optimal.
I am writing, well actually enhancing, a script to do a daily backup of important data on my PC to a second hard drive.I wish to tar my home directory to a single file - and will probably use gzip as well.So I decided to work out the correct tar syntax in a terminal first - here is what happened.I opened a terminal window.I cd to a directory not part of my home directory.I issued the command..Quote: tar -cvf mytar.tar /home/ken tar processed a bunch of files, the last being .netrc.I examined the tar file and it contains .netrc.The contents of .netrc are correct.I scrolled back through the list of files in the terminal window and do not see any error messages.I guess the question is... how do I determine what file tripped up the tar process?
Is there any way to monitor one process' CPU usage and RAM usage over time on Linux? I am trying to change to a cheaper VPS and need to work out what level of CPU and RAM I need!
Get Fedora 11 and Apache installed. Open web browser and enter http://localhost and I get a "Fedora Test Page" that shows Apache is working (according to the info on the page). It says to put my web documents in /var/www/html/ ... however, as a user I cannot access it (put anything there) and I can't change the permissions (belongs to root) I'd like to run this as an intranet web server in our small ( <100 users) company.
I know the tool system-config-display can tell me all about my display but it's not available on all systems and so I'm looking for alternative ways to get my monitor type. Ideally, I could just look in /proc but I don't see anything there and I would like to be able to do so from a script perhaps written in bash or perl. Is there some place to get this info, say in a config file somewhere?
I just rebuilt my fedora box and I'm having some problems getting dual monitors to work. First, I can't reposition my secondary monitor to be on the left. It thinks it's on the right. I can use xrandr to fix this, but that is annoying. Is there no way to do this in the display properties? Second, maximizing a window makes it go across all screens. I unchecked this option in the display properties.I also unchecked the one for letting windows be in multiple monitors at once, but this still happens.
I installed Fedora 11 on my system (see below) using the i686 DVD. The graphical install worked just fine, and after the system booted back up, the X server was working very well.
There is no boot text. On the other system with Fedora 11, I can see the boot text scroll by in the window and/or a progress bar at the bottom of the monitor during the boot sequence. On this system, the monitor says "No Input", and nothing appears until the login prompt for the X window. I am able to enter the BIOS configuration page and navigate through it without any issues. I can also edit the grub commands before Fedora loads without a problem.
If I boot in text mode, no login prompt appears. If I wait long enough, the monitor enters the power save mode since it is not receiving a signal. I am able to log in to the system with my user name and password, and then start the X server. Once the server starts, the monitor turns back ON and all is well.
From the X window, I use the CTL+ALT+F2 key to enter text mode. The monitor stops responding. If I press the ENTER key a couple of times, then press ALT+F7, I can briefly see the text window with a couple of login prompts before the X window starts responding again.
How can I get the text mode to work? Why is there no input to the monitor when booting?
System: Intel D945GSEJT motherboard with Intel Atom N270 processor 2GB RAM 120GB SATA Hard Drive Fedora 11 i686
My x window system just crashed . i can only log in through a non graphical interface. i logged in through root and was configuring my network settings . when again started my laptop after 2 hours it is giving me this problem.
My system boots, I login and am brought to my desktop. I click on the file system icon in the launcher to open a Nautilus window. The window opens, but is unresponsive (i.e., I can't move it, clicking on the icons does nothing, etc.). If I press the super key to get the dash and the press escape, the window becomes responsive again, just like normal.
If I open a folder in the window, the window becomes halfway unresponsive in that I can't move the window, but I can select more folders and toolbar icons. The top menu no longer appears at this point, and I can't access any of the system icons on the top right of the screen. Alt-F4 closes the window even if the close button doesn't work.As another example, suppose I open a Nautilus window and then a Chromium window. Both are immediately unresponsive. If I super-esc again, I can move the Chromium window around, and it seems to work normally. I can click on the Nautilus window, but it always stays greyed out. Even if I'm clicking on things in it, the Chromium window always has focus.
I had a similar experience to this with VLC and Chromium. After clicking around enough I eventually got it to the point where VLC apparently always had focus, but I couldn't access any of VLC's controls. Double clicking anywhere on the screen fullscreened the video, and that's all I could really do. Not even escape worked to bring it back.I can usually press super to get the dash and Alt-F2 to get a command prompt. Also Alt-Shift-T seems to usually work to bring up a working Terminal (at least one that accepts commands, even if I can't move the window).Does anyone have any ideas on what might be causing this? The behavior is highly unpredictable and extremely frustrating. I should note that key commands don't always work, even though they seem to in my examples. So I don't think it's just a mouse issue.
I have a display problem since updating to Slackware 13.37. Everything was fine on Slackware 13.1, but when I switched to 13.37 some piece of software came up with the wrong monitor size. I have a 1600x900 LCD monitor but the X screen came up as 1024x768 with blackness on either side of it. Under Slackware 13.1 the X screen came up as 1600x900 as it should without any prompting from me; I didn't even have an Xorg.conf file. I tried using the Xorg.conf file which was needed and work for older Slackwares, eg 12.*, but it didn't work. (Saying it didn't work is a gross understatement! That old Xorg.conf completely screwed up mouse, keyboard, and monitor; the screen was flashing and nothing worked. The only way to get control back was to SSH into the machine from my laptop and reboot. Killing the X server via that SSH console did NOT the flashing or get me back to my console login; only reboot worked.)
I find I can get the screen to be the right size manually by going through KDE's "System Settings" --> "Display and Monitor" --> "Size & Orientation", then disabling "LVDS1" and setting VGA1 to 1600x900. The size of my odd-sized monitor is being correctly detected for the "Auto" choice. Upon reboot LVDS1 stays disabled but VGA1 reverts to 1024x768 so I have to do this each time.I've done some search of the on-line literature regarding the error messages I am seeing in the boot log.
People are suggesting changing all kinds of things to alleviate the side effects of the "conflicting" error message above, even modifying GRUB parameters (which won't work for me since I use LILO).So, I have a manual work around which I must do each time I log in. Does someone know how I can get X or KDE to force 1600x900 upon start (while Linux/X/whoever find and fix the problem) or does someone know of a real fix?
I recently installed FC14 on my system as I was previously on FC8. Everything seems to be working fine, but I ran into an issue today where I wanted to kill firefox. I checked in gnome system monitor and I did not see a running process for firefox or firefox-bin. I also ran a "ps -e" command from a terminal as root and did not see it there either. I don't know if this is a fedora issue or a firefox issue, so I am posting it here first.
And just to vent on something that IS a firefox issue. I have the new firefox 4 running and when I click the X in the top corner, it doesn't give me the option to save my current tabs and exit like the previous versions did. That was a feature I liked.
can anyone please tell me which package provides the gnome system monitor applet (the one which can display cpu load and disk I/O in the tray)?I run XFCE on F14/x64 and would like to display it using the XfApplet.
What i've tried already: *) Installed the "GNOME Desktop Environment" --> Nothing changed *) did a yum provides "/usr/lib64/bonobo/servers/*" to check which packages are providing applets - didn't found anything which sounds like the system monitor applet
The XfApplet shows up a bunch of available applets but not the system monitor ...
Since one of the recent updates, I cannot close the System Monitor anymore. Opening it, no problem. All processes are listed just fine and I can force close anything that gives me trouble but... When I want to close System Monitor again, nothing. Qtrl + Q, the X close button at the top right, Alt + F4... all do nothing. And although each time I see some disk activity, there is nothing in the logs.
Another thing I notice is that both dbus-daemon and gnome-system-monitor use about 40% CPU time each, taking the system to 100% CPU usage all the time.Luckily, I have System Monitor open so I can select the process gnome-system-monitor from the list and hit Terminate Process. I did not find anything about it in these forums. Anyone noticed this too or am I the only one?
I have persistent video tearing my second monitor (Mitsubushi HDTV). I have tried everything that was suggested with some improvement. I have no issue with tearing if I add the following to my xorg.conf
Is it possible to disable composite for one monitor only and keep it for the other. Or at lease is it possible to have compiz for one monitor only and disable it for the other.
