Stupid work-around for bug #838. The troublesome condition is known, I just
don't know exactly how BitlBee gets into it. Any more info from people who
see this problem often would be useful.
(No files)
Note: See TracChangeset
for help on using the changeset viewer.
