I haven't been able to reproduce this bug since the upgrade to gamin 0.0.26-0ubuntu1. I don't know if it means it has been solved with this new upstream version, or simply that I haven't been lucky enough yet to re-experience the bug.
I haven't been able to reproduce this bug since the upgrade to gamin
0.0.26-0ubuntu1. I don't know if it means it has been solved with this new
upstream version, or simply that I haven't been lucky enough yet to
re-experience the bug.