[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mandrake-cooker
Subject:    [Cooker] [Bug 10307] [Eterm] UNCONFIRMED: Eterm sometimes not killable
From:       "[dvgevers]" <bugzilla () qa ! linux-mandrake ! com>
Date:       2005-03-31 22:08:07
Message-ID: bug10307.20050331220807.694554 () qa ! linux-mandrake ! com
[Download RAW message or body]

User ID: 7681, 128 bugs reported (57 fixed, 7 duplicate, 17 invalid), 434 comments.

http://qa.mandrakesoft.com/show_bug.cgi?id=10307


dvgevers@xs4all.nl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|0.9.2-6mdk                  |0.9.3-1mdk




------- Additional Comments From dvgevers@xs4all.nl  2005-04-01 00:08 -------
Still valif for current version. Happens only rarely but still does.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: baudens@mandrakesoft.com
status: UNCONFIRMED
distribution: cooker
creation_date: 
description: 
24/24 I run seti@home via a very simple script I wrote, in an Eterm window which
invokes another one for seti (Eterm -e ...). When I wish to stop the script &
seti I run the command "skill -c scriptname && skill -c seti". [ Perhaps this
can be done more efficiently, but I like it this way ]. 
During the past month or so I have on 3 separate occasions had a situation where
I could not kill Eterm unless I went to runlevel 1. So, this seems to have krept
in in one of the very last versions, because I am using the same script for ~16
months now and it didn't happen before. I realize this may be quite difficult to
reproduce, but felt it should be brought to your attention anyway.
Thanks and bye.

[prev in list] [next in list] [prev in thread] [next in thread]