Hi,
I can see that this bug is fixed in the development trunk which uses the version number 0.4.2, but that does not seem to be announced as THE 0.4.2 release. Ubuntu then still uses 0.4.1 which has this bug... Is there a chance to update the Ubuntu package so the fix is available for everyone?
Hi,
I can see that this bug is fixed in the development trunk which uses the version number 0.4.2, but that does not seem to be announced as THE 0.4.2 release. Ubuntu then still uses 0.4.1 which has this bug... Is there a chance to update the Ubuntu package so the fix is available for everyone?