Your message dated Wed, 3 Jan 2007 20:22:38 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fvwm95
Version: 2.0.43ba-8
Hi,
for some reason, and with no noticeable advice, from time to
time the fvwm95 TaskBar begins to ¨eat¨ CPU time (its usage
may get as high as 80 or 90% in my 486/100... In fact, it seems
to use ALL CPU it can find, leaving less than 1% idle).
This happens in ¨random¨ moments, and usually just killing
and reloading the TaskBar does the trick, although some times
it refuses to get killed with a 15 signal (even with the TaskBar
disappearing from the screen, the proccess keeps alive - and
eating CPU) and only an abort (9) signal can manage to kill it.
Unfortunately, I can't find any reasonable clue to give for, as
I've said, the problem seems to come out from nothing.
Hope this can be solved soon!
Guilherme Zahn
--- End Message ---
--- Begin Message ---
fvwm95 has been removed from Debian unstable/tesing because it's
unmaintained and abandoned upstream. Please move to fvwm2. If your
bug also shows up in fvwm2 please file a new bug report or let me
know.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
