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.
Now, there is no more TV-Browser in KSysGuard, but the program window is still there (I can move it to another Desktop and get it out of the way) .
Anyone understand what's happening?
Thierry
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.
On Sunday 14 March 2021 12.07:30 Steven D'Aprano via tde-users wrote:
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:
I know about kill, just usually use KSysGuard...
I'll try to investigate next time. although usually KSysGuard does work. TV-Browser is Java. I never really liked Java.
Thierry
On 2021-03-14 05:09:37 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.
Now, there is no more TV-Browser in KSysGuard, but the program window is still there (I can move it to another Desktop and get it out of the way) .
Anyone understand what's happening?
Thierry
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
On Monday 15 March 2021 09.19:58 J Leslie Turriff 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).
Maybe xkill? That's what my search returned. Seems interresting, but of course TV-Browser refuses to hang now :)
Thierry
On Monday 15 of March 2021 09:19:58 J Leslie Turriff wrote:
On 2021-03-14 05:09:37 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.
Now, there is no more TV-Browser in KSysGuard, but the program window is still there (I can move it to another Desktop and get it out of the way) .
Anyone understand what's happening?
Thierry
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
I like killing windows using a killer who is invoked by pressing Ctrl+Alt+Esc :)
Cheers
Anno domini 2021 Mon, 15 Mar 03:19:58 -0500 J Leslie Turriff scripsit:
On 2021-03-14 05:09:37 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.
Now, there is no more TV-Browser in KSysGuard, but the program window is still there (I can move it to another Desktop and get it out of the way) .
Anyone understand what's happening?
Thierry
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).
xkill
The ultimate solution :)
Nik
Leslie
openSUSE Leap 15.2 x86_64 Qt: 3.5.0 TDE: R14.0.9 tde-config: 1.0 ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 2021-03-15 04:39:26 Dr. Nikolaus Klepp wrote:
From: "Dr. Nikolaus Klepp" office@klepp.biz To: users@trinitydesktop.org
Anno domini 2021 Mon, 15 Mar 03:19:58 -0500
J Leslie Turriff scripsit:
On 2021-03-14 05:09:37 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.
Now, there is no more TV-Browser in KSysGuard, but the program window is still there (I can move it to another Desktop and get it out of the way) .
Anyone understand what's happening?
Thierry
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).
xkill
The ultimate solution :)
Nik
It's never been clear to me if xkill kills only an application's X resources, or the whole app.
Leslie
-
Dr. Nikolaus Klepp -
J Leslie Turriff -
Slávek Banko -
Steven D'Aprano -
Thierry de Coulon