** Changed in: gtk-vnc (Ubuntu Hardy)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206227
Title:
vinagre fails to connect
To manage notifications about thi
Anyone listens ?
Drop this c&@p from the default install.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
It seems this problem repeats itself with every release. Here I am in
Maverick and having the same problems as 2 years ago.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: vinagre
Importance: Unknown => Medium
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
** Branch linked: lp:ubuntu/hardy-proposed/gtk-vnc
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
Couldn't agree more. It's half made product which shouldn't be released when
Terminal server client does the job.
There is still international keyboard support issue that makes it completely
useless for non-english users.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You r
Why not just drop vinagre ? It's broken since the beginning, never
worked properly. It's presence in the stable releases (and in the LTS
too !) is not justified.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubunt
With Intrepid, Connecting to a mac, I get "Authentication method to
host "xxx.xxx.xxx:5900" is unsupported. (30)
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Martin Pitt wrote:
> gtkglext promoted to main. Please reopen if there are still problems
> with building this.
>
> What's the fix in 0.3.6? Can it be backported to hardy?
It was supposed to be
debian/patches/from_upstream_fix_vinagre_connection_lp_206227.patch (see
comment 24)
Jonh, do you hav
gtkglext promoted to main. Please reopen if there are still problems
with building this.
What's the fix in 0.3.6? Can it be backported to hardy?
** Changed in: gtk-vnc (Ubuntu)
Status: Fix Committed => Fix Released
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You re
0.3.6 in Intrepid is supposed to fix this. Marking as fix committed for
now as it's dep-waiting on libgtkglext
** Changed in: gtk-vnc (Ubuntu)
Status: Confirmed => Fix Committed
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because y
Reopening, since the current SRU did not fix it.
** Tags removed: verification-needed
** Changed in: gtk-vnc (Ubuntu Hardy)
Status: Fix Committed => Confirmed
** Changed in: gtk-vnc (Ubuntu)
Status: Fix Released => Confirmed
--
vinagre fails to connect
https://bugs.launchpad.net/
In as much as it didn't work before, and it still doesn't work in the
same way, then Yes I suppose there aren't any regressions for me :-)
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Crispin,
Does it work as before then (i.e. no regressions?). That gtk-vnc update
fixes two other issues, so if it doesn't introduce any regressions we
will move it to hardy-updates, even if it doesn't fix this bug.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received t
Accepted into -proposed, please test and give feedback here
** Changed in: gtk-vnc (Ubuntu Hardy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a
0.3.5 synced to Intrepid, the SRU for hardy is on its way (see bug
206227)
** Changed in: gtk-vnc (Ubuntu)
Status: Fix Committed => Fix Released
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, w
debdiff attached for hardy-proposed:
gtk-vnc (0.3.4-0ubuntu2) hardy-proposed; urgency=low
* Cherry-pick fixes from upstream:
- from_upstream_fix_crash_on_closing_connection_lp_207205.patch:
+ Fixes a crash when closing the connection on the middle of an
update. LP: #207205.
thanks for your interest on getting the issue fixed, I've opened an
hardy task now
** Changed in: gtk-vnc (Ubuntu Hardy)
Importance: Undecided => High
Status: New => Confirmed
** Changed in: vinagre (Ubuntu Hardy)
Importance: Undecided => Low
Status: New => Invalid
--
vinagr
I don't know what the process for this is, but somebody in Ubuntu should
really consider pushing this fix into a Hardy Heron update.
.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Changed in: vinagre
Status: New => Fix Released
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
interim_descriptor wrote:
> I don't know what the process for this is, but somebody in Ubuntu should
> really consider pushing this fix into a Hardy Heron update.
I opened bug 218667 for updating gtk-vnc for Hardy, but it was too late and it
introduced some regressions so this won't probably hit h
Jonh Weldell:
That patch, applied to my svn/hg version of vinagre + gtk-vnc, did the
trick!
Vinagre was able to connect to my OSX box without any further trouble.
Thanks for fixing that.
I don't know what the process for this is, but somebody in Ubuntu should
really consider pushing this fix i
We still don't support this auth method (30). But I have made a patch
that should work in cases where the server supports more than one auth
type.
The patch:http://gtk-vnc.codemonkey.ws/hg/outgoing.hg/rev/e1b964facd65
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You receive
I'd like to back up Xamusk's opinion on this.
Does anybody have a work-around for this, in the meantime?
I am able to replicate Nick Barcet's steps, and verify that the error
message does in fact change to:
Authentication method to host "192.168.1.108:5900" is
unsupported. (30)
More in
Hardy was released with this bug!
As mentioned above, it's unbelievable that a LTS release admits as default a
program that won't connect even with the previous Ubuntu version.
That one can install another program later is not an excuse. Remember it's a
default app, and as such people will usuall
But why does it work right after connecting with vncviewer ?
Connecting to a host with xtightvncviewer (which always works) triggers vinagre
to also work for that target.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a membe
Connecting to a mac, updating gtk-vnc to the version in your ppa did change the
error message to "Authentication method to host "xxx.xxx.xxx:5900" is
unsupported. (30)", but did not solve the issue.
(I guess I did not need to reboot after applying the package).
--
vinagre fails to connect
https
Please, see bug 218667 where I request an exception to get an update for
gtk-vnc fixing this bug. There's a link to my ppa which has the update,
so please test it and comment on that bug.
Thanks
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification
Raising importance to high as this makes Vinagre unusable in some cases
and is a regression wrt xvncviewer.
** Changed in: gtk-vnc (Ubuntu)
Importance: Low => High
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of
** Attachment removed: "signature.asc"
http://launchpadlibrarian.net/13534691/signature.asc
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
gtk-vnc 0.3.5 fixes this bug, along with other one related to wrong
colors (bug #212504).
What I mean in my previous comment is: If you are going to update gtk-
vnc to 0.3.5, you need to apply that patch in vinagre, in order to have
debug stuff enabled. Having debug stuff enabled is mandatory!
Al
Jonh,
I guess it's too late to update gtk-vnc at this point. RC is this Friday and
final release next Thursday...
We already have vinagre 0.5.1, and that patch is only for debugging purposes?
If so, it's not probably worth the risk at this point (without looking at the
diff, svn.gnome.org isn't
IMHO, Ubuntu Hardy should come with gtk-vnc 0.3.5, and vinagre 0.5.1
with this patch:
http://svn.gnome.org/viewvc/vinagre?view=revision&revision=273
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which
If a definitive fix will not make it to hardy, then at least vinagre should be
demoted from the default vnc client position. I want to remind everybody that
this release is LTS and it would be very lame to ship something that is
installed by default and by default it does not work.
Thank you.
Matthew Tighe wrote:
> Is this fix going to make into Hardy or Hardy.1?
Unfortunately it won't, as this requires a new version of gtk-vnc which we won't
introduce at this stage.
>
> If not, I think you should simply remove it. It doesn't really work.
I'm sorry it doesn't work for this case, bu
Is this fix going to make into Hardy or Hardy.1?
If not, I think you should simply remove it. It doesn't really work.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have just found a very weird thing :
1. Try to connect using vinagre a few times. I get "the connection was closed"
every time.
2. I try to connect using vncviewer (from xtightvncviewer ) and this works fine.
3. I close vncviewer and get back to vinagre and try to connect again using
vinagre.
Hey guys. Just an FYI this will not connect to a host running Leopard
either. krdc connects just fine, but vinagre just quits saying it could
not connect to the host. It finds it though when you browse.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notif
I am curious if this is going to be fixed for hardy release. Otherwise
it would be quite ridiculous to have a default vnc client that is not
even able to connect to the previous version of ubuntu...
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notificat
I experience the same behavior when using vinagre "against" two different
linux host, both running ubuntu gutsy.
It is also important to note that given a significant number of retries the
connection will eventually succeed.
Using
ii vinagre0.5.0-1VNC client for the GNOME Deskt
Hi, Emilio, I always get confused about fix commited vs released :)
Sure this is stuff for Hardy+1, I do not guarantee that Vinagre 0.5 will
run fine with that new version of gtk-vnc.
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because yo
(let's leave the Ubuntu task open until the fix reaches the
repositories, which I assume will be Intrepid as gtk-vnc introduces so
many changes (and hasn't even been officially released yet))
** Changed in: vinagre (Ubuntu)
Status: Fix Released => Fix Committed
--
vinagre fails to connect
OK, This issue has been fixed in gtk-vnc development version. The fix
will be available in the next vinagre version.
** Changed in: vinagre (Ubuntu)
Status: Triaged => Fix Released
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification becaus
Jonh Wendell <[EMAIL PROTECTED]> writes:
> James, could you please paste here the output of xvnc4viewer with that
> machine?
| $ xvnc4viewer localhost:5900
|
| VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
| Copyright (C) 2002-2005 RealVNC Ltd.
| See http://www.realvnc.com for
James, could you please paste here the output of xvnc4viewer with that
machine?
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
It seems vinagre can't connect to v3.3 or older clients!!! I've tried to
connect to RealVNC and TightVNC servers and it always give up with
connection to host was closed. It connects right away with another hardy
heron machine.
This is essential to my work where I have to connect to hundreds of
co
** Changed in: vinagre (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Triaged
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
** Changed in: vinagre
Status: Unknown => New
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
** Bug watch added: GNOME Bug Tracker #521631
http://bugzilla.gnome.org/show_bug.cgi?id=521631
** Also affects: vinagre via
http://bugzilla.gnome.org/show_bug.cgi?id=521631
Importance: Unknown
Status: Unknown
--
vinagre fails to connect
https://bugs.launchpad.net/bugs/206227
You
49 matches
Mail list logo
