Hi!
Since this bug was closed automatically and not marked fixed, I wonder if it is still an issue since I am still using 0.6.3 (from feisty, where the bug is still there) and do not want to upgrade without knowing that it will be worth the hassle...
Hi!
Since this bug was closed automatically and not marked fixed, I wonder if it is still an issue since I am still using 0.6.3 (from feisty, where the bug is still there) and do not want to upgrade without knowing that it will be worth the hassle...