My install of jaunty suffers as well of this bug.
What I do not really get is why canonical, who actually pay people to do make a decent distro, do not simply acknowledge the bug, check with upstream, fix it in svn, and ship the updated package?
Or is it because in this particular case the package we talk about has been coded by opensuse/novell mainly?
My install of jaunty suffers as well of this bug.
What I do not really get is why canonical, who actually pay people to do make a decent distro, do not simply acknowledge the bug, check with upstream, fix it in svn, and ship the updated package?
Or is it because in this particular case the package we talk about has been coded by opensuse/novell mainly?