Thanks for the quick response! Any chance that the bugfix will trickle downstream via the normal 10.10 update process? The newest version (1.8.0-2ubuntu1~maverick1 from the maverick-updates repository, available this morning) still exhibits this bug.
Thanks for the quick response! Any chance that the bugfix will trickle downstream via the normal 10.10 update process? The newest version (1.8.0- 2ubuntu1~ maverick1 from the maverick-updates repository, available this morning) still exhibits this bug.