Well, I don't think this needs a fix, since version 0.2.4 is working without any modifications - recompiled or from repositories. Probably this was fixed in between, or the 0.2.0 version was compiled against a buggy lib or something. Don't know for sure.
Well, I don't think this needs a fix, since version 0.2.4 is working without any modifications - recompiled or from repositories. Probably this was fixed in between, or the 0.2.0 version was compiled against a buggy lib or something. Don't know for sure.