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 736099 - cannot connect to password protected vnc
cannot connect to password protected vnc
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
3.13.x
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-09-05 06:40 UTC by vladimir benes
Modified: 2016-09-20 08:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description vladimir benes 2014-09-05 06:40:58 UTC 
I cannot connect to password protected vnc server. I think the problem is more generic and not connected to vino but affecting all password protected vnc connections. 

version:
3.13.91

1. start vino server with password
2. connect to it from gnome-boxes

result:
crash
Comment 1 vladimir benes 2014-09-05 06:41:44 UTC 
more information (backtrace) should be stored here:
https://bugzilla.redhat.com/show_bug.cgi?id=1136229
Comment 2 Zeeshan Ali 2014-10-24 18:26:58 UTC 
commit: 91fdebe13f57d7ef8cc3eb581e4c2f10e41bce64

    vnc-display: Correct arguments to a signal handler
    
    Correct arguments to handler of Vnc.Display.vnc_auth_credential signal.
    
commit: 709d5ad596d4089ea37b9b2208bd48feb10d6ac6

    vnc-display: Correctly cast to DisplayCredential
    
    DisplayCredential is not a class so you can't use 'as' operator to cast
    to this type.
    
    This together with previous patch, fixes a crash that always happens if
    you try to connect to a VNC box that has password on it.
Comment 3 Zeeshan Ali 2014-10-24 18:30:49 UTC 
While trying to reproduce this bug after fixing it, I managed to create an infinite recursion of Boxes inside Boxes.. :)