Fixed with the sync of 0.3.1-1 from Debian.
** Changed in: gtk-vnc (Ubuntu)
Status: Invalid => Fix Released
--
Please sponsor gtk-vnc_0.3.0 into Hardy
https://bugs.launchpad.net/bugs/176005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
** Changed in: gtk-vnc (Ubuntu)
Status: Incomplete => Invalid
--
Please sponsor gtk-vnc_0.3.0 into Hardy
https://bugs.launchpad.net/bugs/176005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
Sorry, it's a upstream bug.
http://bugzilla.gnome.org/show_bug.cgi?id=503316
--
Please sponsor gtk-vnc_0.3.0 into Hardy
https://bugs.launchpad.net/bugs/176005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Thank you for your work there, did you try to build the update though?
The new tarball seems to be broken and configure doesn't work, what did
you do to get it building?
** Changed in: gtk-vnc (Ubuntu)
Importance: Undecided => Low
Status: New => Incomplete
--
Please sponsor gtk-vnc_0.3
Sorry, bug spam necessary because of bug 176085.
This bug has a patch attached, which needs review and sponsoring.
--
Please sponsor gtk-vnc_0.3.0 into Hardy
https://bugs.launchpad.net/bugs/176005
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
http://revu.tauware.de/details.py?upid=964
** Attachment added: "gtk-vnc_0.3.0-0ubuntu1.interdiff"
http://launchpadlibrarian.net/10868911/gtk-vnc_0.3.0-0ubuntu1.interdiff
--
Please sponsor gtk-vnc_0.3.0 into Hardy
https://bugs.launchpad.net/bugs/176005
You received this bug notification becau
