<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:10pt;font-family:Sans Serif">
<p>Am Mittwoch, 21. April 2010 12:07:17 schrieb Bernhard Reiter:</p>
<p>> > * We see some https://issues.kolab.org/issue4302 (Kleo keylisting hangs</p>
<p>> > after using Kleo for a while (killing gpgsm helps)) and we do not know if</p>
<p>> > this is more fequent with 2.0.2rc2 compared to 2.0.1.</p>
<p>> > Does somebody see those hangs with 2.0.1, too?</p>
<p>></p>
<p>> As you know, we did the 2.0.2 release. Frequency of this defect to show is</p>
<p>> comparitively low and the advantages outweight the drawbacks.</p>
<p>></p>
<p>> However it seems that we have found a source for the 4302 hang defect,</p>
<p>> so we need to decide if we should do a 2.0.3. (The code is in trunk, we</p>
<p>> need to see if 2.0.2+patches would fully resolve the issue.)</p>
<p></p>
<p>As you can see from the issue4302, the current patch we have makes the hang less likely, but it is not completely gone. So what speaks for releasing 2.0.3 with the patch is that 2.1.0 is a bit away. On the other hand, the checks for is_socket() that are introduced by the patch could potentially resolve the hang completely if we find the remaining places where we need to apply the same technique.</p>
<p></p>
<p>Best,</p>
<p>Bernhard</p>
<p></p>
<p>-- </p>
<p>Managing Director - Owner: www.intevation.net (Free Software Company)</p>
<p>Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.</p>
<p>Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998</p>
<p>Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner</p>
</body></html>