I believe that this has been fixed in the new upstream release (1.2.3 onwards). This update is currently awaiting upload at bug #229360.
I believe that this has been fixed in the new upstream release (1.2.3 onwards). This update is currently awaiting upload at bug #229360.