Comment 7 for bug 640398

Now I'm using the version 2.2.1~0alpha0: the problem persists