Comment 1 for bug 206960

Dan O'Reilly (oreilldf) wrote :

I noticed this with 1.4.2 and lower as well. I haven't experienced it while I've been running the 1.5.0 daemon (though I haven't been paying close attention to it), so there's a good chance it's fixed. Not 100% sure though, once 1.5.0 gets released give it a shot and see how it runs.