[climm] endless loop

[Stanimir Dragiev]

Hello,

Last days I experience a very strange behaviour when messaging:

Often (nearly always) after receiving message from somebody other than me
climm enters an endless loop, using 100% of the CPU and must be killed
explicitly in order to stop (closing the terminal does not work)

I use rxvt-unicode and its client-daemon architecture (urxvtd in background
and urxvtc to start new client terminal). This behaviour caused my urxvtd
to become unable to serve new terminal requests and all terminals were
blank... Since I was not sure what caused the problem  I killed urxvtd
(eventually loosing unsaved work in terminals).

At some point I noticed that all this happens when I receive message and I
tried the following: inside the terminal I started screen and from screen I
started climm. Then asked somebody to send me a message. The result was
climm entering the endless loop like before, but I was able to kill it and
return to screen.

Before experiencing this first time, I haven't changed anything in the
climm configuration, AFAICR. I think, on the day before that, I did an
update which may have pulled new rxvt-unicode packages. But it is strange,
that climm, not urxvtd should be killed.

[ ... some  minutes later ]

I tried the same in xterm and succeed to reproduce it. So it's not an urxvt
issue, as it seems.

Do you have any clue ...

I run
Debian lenny, kernel 2.6.26-1-686, 
rxvt-unicode 9.05-1
climm last release
and
svn co http://svn.climm.org/climm/

Thanks a lot for any suggestions!

-- 
 cheers
 stanio_