This problem is still present in ubuntu 17.10, eleven years after the bug was created. How can this be solved? Is there a similar bug in the gnome bug tracking tool?
This problem is still present in ubuntu 17.10, eleven years after the bug was created. How can this be solved? Is there a similar bug in the gnome bug tracking tool?