It seems to be fixed. I didnt realize the package had been updated. Now I have 0.11.5
On Wed, 2009-03-11 at 13:00 +0000, Ville Ranki wrote:
> I haven't seen this problem any more on Intrepid for a while. Has it > been fixed or does someone still have it? >
It seems to be fixed. I didnt realize the package had been updated. Now
I have 0.11.5
On Wed, 2009-03-11 at 13:00 +0000, Ville Ranki wrote:
> I haven't seen this problem any more on Intrepid for a while. Has it
> been fixed or does someone still have it?
>