On Fri, 2005-08-12 at 18:07 +0100, Daniel Glassey wrote:
I still haven't worked this one out. I've uploaded gnomesword 2.1.2. Any
chance this has fixed it?
Daniel,

I have 2.0.0-6 now, and it's not reproducible in this version, so whatever the issue was with GNOME has apparently already been resolved (possibly by merely recompiling 2.0.0, as you said you would do).  So go ahead and close the bug.

Looking forward to 2.1.2 when it hits the archive.

Thanks,
Ben

Reply via email to