kill user manager

slybloty · #1 24th April 2012, 02:38 PM

After I changed my password on Fedora 15, the gnome-shell has crashed and the User Manager application has frozen and can't close it. I would like to kill it but I have no idea what it's called and what process to look for. Any ideas?

nonamedotc · #2 24th April 2012, 02:56 PM

I believe you are looking for system-config-users.

slybloty · #3 24th April 2012, 03:00 PM

It's not listed. I thought the same way. This is what includes system:

Code:

$ ps -e | grep system
    1 ?        00:00:25 systemd
  487 ?        00:00:00 systemd-logger
 1056 ?        00:00:00 system-setup-ke
 3090 ?        00:00:00 system-config-f

nonamedotc · #4 24th April 2012, 03:05 PM

Alright. Search for gnome-control-center. You used the username on the top right corner to reach user management I presume?

slybloty · #5 24th April 2012, 03:56 PM

I've opened the Users and Groups application which is system-config-users. But now it doesn't show under processes anymore.
Here's that I get:

Code:

$ ps -e | grep gnome
 1017 ?        00:00:01 gnome-keyring-d
 1025 ?        00:00:01 gnome-session
 1263 ?        00:00:17 gnome-screensav
 1265 ?        00:00:09 gnome-power-man
 1379 ?        00:00:00 gnome-pty-helpe
26847 ?        00:04:01 gnome-shell
26868 ?        00:00:00 gnome-shell-cal
30541 ?        00:00:00 gnome-settings-

---------- Post added at 08:56 AM ---------- Previous post was at 08:26 AM ----------

I got it. It was a python2 process that I had to kill.

nonamedotc · #6 24th April 2012, 04:00 PM

what process was it? Just to know!

slybloty · #7 24th April 2012, 04:14 PM

I had to

Code:

killall python2

in order to close that window completely.

jpollard · #8 24th April 2012, 04:50 PM

It might have been easier with a "ps -ef", which gives the full format listing with the command and options.

Alternatively, to close a window forcefully you can try "xkill" and point to the window.

Xkill causes the X server to close the window, and presumably the application will then exit. This is not guaranteed, as many applications do not properly use the events - and keep trying to send data.... sucking up 100% of a CPU in the process.

When this happens I use "top" to see what is the pig, and if it is my process, I can kill it then (k, and it will prompt for the process id, then what signal to send - I usually use 9).