On Sun, Mar 14, 2021 at 11:09:37AM +0100, Thierry de Coulon via
tde-users wrote:
> Hello all,
>
> I use (a little) a program named "TV-Browser" that regularely has trouble
> closing.
>
> Now I see this: TV-Browser completely crashed on quit. So I fired KSysGuard
> and killed it.
If you needed to kill it with KSysGuard, then it hadn't completely
crashed. Something was still running. It's too late to find out what
now, because you killed it.
My guess is that your TV-Browser application consists of at least two
processes, one is the process you killed, and the other is the GUI.
Another possibility is that KSysGuard was not, in fact, able to kill the
process. In general, when killing processes from the command line, one
uses the "kill" command with the process ID, and does it in three steps
(if necessary), in increasing levels of severity:
# Ask the process nicely to please quit.
kill processID
# If that fails, slap it around the head and shout at it.
kill -HUP processID
# If, and only if, that fails to, hit it with an axe.
kill -9 processID
I imagine that KSysGuard starts at the first level, which is the correct
thing to do, but that is sometimes not sufficient to properly force the
process to quit. And there may be other processes involved.
At the command line, can you run:
ps aux | grep -i tv-browser
and see if there is anything still running with "tv-browser" in its
name. Of course, there is no guarantee that whatever it is running has
that in its name.
You can also use the top command to see what's running.
--
Steve
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
