Comment 1 for bug 763467

Hi there,

Thank you for taking the time to report bugs and trying to make Ubuntu better.

Unfortunately,. I've been unable to reproduce this error. However, after some online research this problem appears to be with version 1.1.17 and maybe 1.1.18. Starting from 1.1.19 this seems to be fixed. Unfortunately there doesn't seem to exist a patch to fix this issue specifically but rather just to use a newer upstream version according to what I've read.

For now, I'll be marking this bug as incomplete until a bit more research is done in the issue and maybe finding the appropriate patch in upstream.