has the bug been fixed in the upstream svn? that would be something that could be consider for a stable update if somebody wants to work on it, the desktop team has limited ressources and lot to do and intrepid is not a lts
has the bug been fixed in the upstream svn?
that would be something that could be consider for a stable update if somebody wants to work on it, the desktop team has limited ressources and lot to do and intrepid is not a lts