So I'd like to manage my autostart applications and e.g. disable those which I prefer not to autostart. How can I do that in Debian 9.0? I could not do so via the System Monitor and I'd prefer a GUI over the console. In KDE's System Settings most of the autostarting software is not shown under Autostart (issue here ). Furthermore it would be nice if such a tool also displayed some information about the apps/processes such as what they do, whether they're safe to disable and e.g. things like whether many have them running as well and whether (many/specific) users have flagged them for being undesired.

I am using FreeBSD on a personal desktop computer, and a nvidia GTX 1650 GPU. In my gnome system monitor (similar to task manager of MS Windows), I am able to monitor all the resources, including all the processor cores, RAM, swap memory, and other stuff. But GPU is not visible there. Is there any tool for FreeBSD to see the GPU activity/usage? GUI based is preferred, but CLI is ok as well. I did a lot of research, but could not find anything to monitor GPU usages. I do not want to over-clock the GPU. I want to only monitor it.

Is there a way to prevent [Gnome System Monitor](https://wiki.gnome.org/Apps/SystemMonitor) from providing kill option in the context menu for a given process ? If you can't help but asking why I want this, I was assigned the (perplexing) task of trying to prevent the execution of kill [specific process] for root/users with elevated privileges throughout the system. Apart from this sounding illogical, I have been reading posts that describe that this is not only not possible but detrimental. So I decided to approach this by collecting evidences to corroborate the inviability of this, by breaking it into: 1. prevent execution of kill from command line 2. **prevent killing of process from GUI** 3. prevent stopping systemd 4. in my app (a .NET app which runs as a systemd daemon), intercept the kernel signal sent to the process upon running kill (perhaps calling sigaction) so to ignore the kill request. This question tries to clear item number 2: does System Monitor offer the possibility of hiding/customizing commands from its context menu, such as kill, out-of-the-box ?

Suppose multiple processes are using the same shared library (such as Gtk). Presumably, they mmap the library file, and physically, the RAM is shared? However, the size of the library gets added to each process's memory size, as shown in the system monitor, leading to exaggerated numbers. Is this accurate?

I have Debian 10 & KDE Plasma. Sometimes when I double-click the icon in KDE to start Gnome System Monitor it appears to load and then immediately closes. When I try to start from the command line by entering gnome-system-monitor I get this: (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.441: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.441: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.441: Theme parsing error: gtk.css:129:34: The style property GtkCheckButton:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.441: Theme parsing error: gtk.css:130:36: The style property GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.441: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.442: Theme parsing error: gtk.css:135:30: The style property GtkExpander:expander-size is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): Gtk-WARNING **: 15:21:17.442: Theme parsing error: gtk.css:142:29: The style property GtkStatusbar:shadow-type is deprecated and shouldn't be used anymore. It will be removed in a future version (gnome-system-monitor:3146): glibmm-CRITICAL **: 15:21:17.486: unhandled exception (type Glib::Error) in signal handler: domain: g-io-error-quark code : 0 what : Unable to find default local file monitor type I'm not sure how it gets into this state where I can't start it, or how to fix it so it can start again. I tried: sudo killall gnome-system-monitor and get this: gnome-system-monitor: no process found

I have Debian 10 and KDE Plasma. gnome-system-monitor had been working perfectly for 10 months, and all of a sudden when I try to open it in KDE I get this error:

gnome-system-monitor
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.934: Theme
 parsing error: gtk.css:127:35: The style property
 GtkButton:child-displacement-x is deprecated and shouldn't be used
 anymore. It will be removed in a future version
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.935: Theme
 parsing error: gtk.css:128:35: The style property
 GtkButton:child-displacement-y is deprecated and shouldn't be used
 anymore. It will be removed in a future version
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.935: Theme
 parsing error: gtk.css:129:34: The style property
 GtkCheckButton:indicator-size is deprecated and shouldn't be used
 anymore. It will be removed in a future version
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.935: Theme
 parsing error: gtk.css:130:36: The style property
 GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used
 anymore. It will be removed in a future version
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.935: Theme
 parsing error: gtk.css:132:46: The style property
 GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't
 be used anymore. It will be removed in a future version
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.935: Theme
 parsing error: gtk.css:135:30: The style property
 GtkExpander:expander-size is deprecated and shouldn't be used anymore.
 It will be removed in a future version
 
 (gnome-system-monitor:28523): Gtk-WARNING **: 14:51:50.936: Theme
 parsing error: gtk.css:142:29: The style property
 GtkStatusbar:shadow-type is deprecated and shouldn't be used anymore.
 It will be removed in a future version
 
 (gnome-system-monitor:28523): glibmm-CRITICAL **: 14:51:50.990: 
 unhandled exception (type Glib::Error) in signal handler: domain:
 g-io-error-quark code  : 0 what  : Unable to find default local file
 monitor type

I have no idea what this means or why it started happening.

Context: I installed ubuntu 18.04 on a lenovo legion y540 laptop with dual hard disks. ubuntu 18.04 on 128GB m.2 and windows 10 on the second drive-ssd. When I installed ubuntu I chose 15GB swap space. The machine has 16GB ram. Problem: When I open system monitor application, it shows the system as 2gb of swap but on the 'disks' app, it shows the swap as 15gb as I allocated. Why is this discrepeancy?

$ sudo du -h -d 0 home/ 309G home/ $ df -h Filesystem Size Used Avail Use% Mounted on ... /dev/sda4 550G 309G 214G 60% /home ... System Monitor on Ubuntu shows the used space on /home is 331.1 GB Do the different ways measure the same thing? How differently do they make the measurements? Thanks.

Recently i've resized my root partition to increment the swap. After the process, gnome-system-monitor doesn't recognize the new status of my partitions, but fdisk shows the updated table whit correct values. I rebooted several times but nothing has changed. Here some screenshot:

So I'd like to gain some insight into which processes (incl. daemons) upload and download how much data on my Debian 9 machine. Sadly the System Monitor does not display such information. I'd prefer a GUI over the console. I have tried nethogs which is probably what people would recommend for such endeavors, however it only shows the *current* network traffic processes instead of cumulative information such as a proper statistic or ordered list. I'm aware of wireshark.

I would like to make the Ubuntu Linux 16.10 System Monitor % CPU utilization measurement basically agree with the ps "pcpu", % CPU utilization for an individual Firefox browser process running on a Lenovo Thinkstation desktop with quad cores. The Ubuntu Linux 16.10 System Monitor Preferences are currently set at: Update interval in seconds: 3.00 Enable smooth refresh: Yes Alert before ending or killing processes Yes Divide CPU usage by CPU count : Yes The ps output for the Firefox process is: $ ps -eo pid,rss,c,pcpu,cputime,cmd | grep firefox 2848 726024 3 3.5 00:50:23 /usr/lib/firefox/firefox -new-window After reading https://unix.stackexchange.com/questions/67647/linux-see-cpu-usage-by-a-process-for-the-last-second , I learned how to view cpu usage for the last second. The top output for the Firefox process is: $ top -b -d 1 | grep -in "firefox" 8: 2848 ratio 20 0 1980240 641516 115240 S 18.8 15.9 73:10.86 firefox For the Firefox browser app, I get 3.5% pcpu from ps -eo pid,rss,c,pcpu,cputime,cmd while for the same Firefox browser app, the GUI Application Ubuntu System Monitor shows 5% CPU utilization. In addition, I get 15.9% CPU usage from top -b -d 1 | grep -in "firefox". When that is divided by 4 for the 4 cores used by our CPU, I get 4.0% for top's output. How can I get the ps or top outputs and System Monitor values to agree? Should I enable the Divide CPU usage by CPU count checkbox?

What is the reason for the following discrepancy between Ubuntu Linux 16.10 System Monitor % CPU utilization and ps pcpu, % CPU utilization with respect to the individual Firefox browser process? For the Firefox browser app , I get 2.8 % pcpu from ps -eo pid,rss,c,pcpu,cmd while for the same Firefox browser app, the GUI Application, Ubuntu System Monitor, show 0 % CPU utilization. May I ask why this difference? An Unix Linux Stack Exchange expert's , @DopeGhoti, hypothesis about this difference is: it could be that ps is reporting actual CPU usage at that moment, but the GUI application could be showing aggregate usage over the last n seconds, or possibly rolling in CPU usage from children or iowait usage. Could someone expand on this hypothesis? Any help is greatly appreciated.

This might be a shot in the dark, but I am wondering if there is a way that I can connect my system monitor on my computer to my headless box. It would be awesome to somehow use that interface display what is going on on my server, from my Desktop. I am of course aware of tools like top and other web based monitors that I could use... but I think it would be cool to use Gnome's.