On Sun, Mar 14, 2021 at 11:09:37AM +0100, Thierry de Coulon via tde-users wrote: 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

On 2021-03-14 05:09:37 Thierry de Coulon via tde-users wrote: It's possible that TV-Browser died but left its Xwindow resources orphaned. There's an X command for killing such orphan windows (but I can't remember its name; sorry). Leslie -- openSUSE Leap 15.2 x86_64 Qt: 3.5.0 TDE: R14.0.9 tde-config: 1.0