After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 509634 - Crash if hostname contains invalid characters
Crash if hostname contains invalid characters
Status: RESOLVED FIXED
Product: gtk-vnc
Classification: Other
Component: general
0.3.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-vnc-maint
gtk-vnc-maint
: 510691 512645 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-15 13:17 UTC by Emilio Pozuelo Monfort
Modified: 2009-02-26 12:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Emilio Pozuelo Monfort 2008-01-15 13:17:57 UTC 
Reported by Soren Hansen, 100% reproducible with Vinagre 0.4.
https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/183169


Click "Connect", enter "localhost:1" in the host field, click "Connect". Boom.

expected result: In a perfect world, it would figure out that I meant to put "localhost" in the host field and 5901 in the port field, but just an error message would be enough to make me happy. For now :)
Comment 1 Jonh Wendell 2008-01-19 22:11:39 UTC 
*** Bug 510691 has been marked as a duplicate of this bug. ***
Comment 2 Claude Paroz 2008-01-21 21:35:44 UTC 
I'm obtaining a segmentation error, too, as soon as I type a non-existent name as the host name. Jonh, can you reproduce it or do you need some sort of bugtrace?
Comment 3 Emilio Pozuelo Monfort 2008-01-21 22:13:14 UTC 
This is fixed by the patch from http://sourceforge.net/mailarchive/forum.php?thread_name=1200593447.11172.6.camel%40wendell-laptop&forum_name=gtk-vnc-devel (attached to https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/183169)

In the end it was a gtk-vnc bug, which should be fixed in 0.3.3
Comment 4 Jonh Wendell 2008-01-21 22:15:50 UTC 
Hi, Claude.

This was a bug in gtk-vnc, which was fixed today [1], in its development trunk. If you can't get it [2], please, wait until 0.3.3 is released, which should happen by the end of the month.

Thanks.

[1] - http://gtk-vnc.codemonkey.ws/hg/outgoing.hg/rev/4fc4541f1ad7
[2] - http://gtk-vnc.sourceforge.net/Code
Comment 5 Claude Paroz 2008-01-22 07:17:58 UTC 
Great. My only concern is that the bug won't be any more in 2.22. Until then, we can live with it :-)
Comment 6 Jonh Wendell 2008-01-28 20:29:03 UTC 
*** Bug 512645 has been marked as a duplicate of this bug. ***