GNOME Bugzilla – Bug 581817
Black screen when entering wrong password
Last modified: 2011-04-17 16:16:05 UTC
vinagre-2.24.2-1.fc10.x86_64 gtk-vnc-0.3.8-4.fc10.x86_64 (The 2 bugs roller into one might already be fixed...) 1. Launch vinagre 2. See the Mac in the "nearby hosts". avahi-browse -ra says: = eth0 IPv4 Bastien Nocera’s Mac mini VNC Remote Access local hostname = [bastien-noceras-mac-mini.local] address = [192.168.1.105] port = [5900] txt = [] 3. Double-click on the bookmark 4. Black screen Connecting via "Machine" -> "Connect" and entering the IP address correctly asks for a password. 2nd (related?) bug: 1. Launch vinagre 2. Machine -> Connect -> 192.168.1.105 3. Get asked for password, enter wrong password 4. Black screen, and no mentions that we entered the wrong password
The first bug is fixed trying out 2.26 in F11, the second one isn't.
Hi, Bastien. Please run vinagre in a terminal with the argument --gtk-vnc-debug and paste here the output. Thanks.
Created attachment 143459 [details] [review] First patch Let's start with that patch to make the activation of mDNS bookmarks 1) not emit warnings 2) actually get through to the signal handlers.
With the above patch, I don't get a request for a password when activating an mDNS bookmark: gtk-vnc: Expose 0x1 @ 1468,892 gtk-vnc: Started background coroutine gtk-vnc: Resolving host bastien-noceras-mac-mini.local 5900 gtk-vnc: Trying socket 19 gtk-vnc: Protocol initialization gtk-vnc: Server version: 3.889 gtk-vnc: Using version: 3.8 gtk-vnc: Possible auth 30 gtk-vnc: Possible auth 31 gtk-vnc: Possible auth 32 gtk-vnc: Possible auth 2 gtk-vnc: Possible auth 35 gtk-vnc: Thinking about auth type 2gtk-vnc: Decided on auth type 2gtk-vnc: Waiting for auth type gtk-vnc: Choose auth 2 gtk-vnc: Do Challenge gtk-vnc: Requesting missing credentials gtk-vnc: Set password credential milhouzegtk-vnc: Waiting for missing credentials gtk-vnc: Got all credentials gtk-vnc: Checking auth result gtk-vnc: Expose 0x1 @ 1468,892 Using the IP address works though.
Patch applies to master as well.
Created attachment 143460 [details] [review] updated patch And you really need to add a real COPYING file to the tree too...
Comment on attachment 143460 [details] [review] updated patch The first two changes are OK, bu the last one no. I want to explicitly pass NULL to the signal. The listener (vinagre-window.c:fav_panel_selected) checks if it is NULL to make some menu items sensitive or not.
NULL isn't a valid object.
Then we should back and pass just pointers to signals, agree?
Created attachment 143462 [details] [review] updated patch You're right, this patch fixes the warnings as expected.
Back to the original bug: 1. Connect to a VNC server with a password 2. Save the password in the keyring 3. Change the password in the keyring using seahorse (or change the remote password on the server) 4. Try to connect to the same VNC server 5. Black screen, and gtk-vnc only asks for authentication once The log says: gtk-vnc: Expose 0x1 @ 1468,892 gtk-vnc: Started background coroutine gtk-vnc: Resolving host bastien-noceras-mac-mini.local 5900 gtk-vnc: Trying socket 19 gtk-vnc: Protocol initialization gtk-vnc: Server version: 3.889 gtk-vnc: Using version: 3.8 gtk-vnc: Possible auth 30 gtk-vnc: Possible auth 31 gtk-vnc: Possible auth 32 gtk-vnc: Possible auth 2 gtk-vnc: Possible auth 35 gtk-vnc: Thinking about auth type 2 gtk-vnc: Decided on auth type 2 gtk-vnc: Waiting for auth type gtk-vnc: Choose auth 2 gtk-vnc: Do Challenge gtk-vnc: Requesting missing credentials gtk-vnc: Set password credential BLAHBLAHBLAH gtk-vnc: Waiting for missing credentials gtk-vnc: Got all credentials gtk-vnc: Checking auth result gtk-vnc: Expose 0x1 @ 1468,892 gtk-vnc: Expose 0x1 @ 1468,892 gtk-vnc: Expose 0x1 @ 1468,892 <black screen> gtk-vnc: Requesting that VNC close gtk-vnc: Requesting graceful shutdown of connection gtk-vnc: Waking up couroutine to shutdown gracefully Does that look like a gtk-vnc bug? gtk-vnc-0.3.9-1.fc12.x86_64
In Vinagre 2.30.3 with gtk-vnc 0.4.2 (and master of both) this seems to be fixed (an authentication error dialog is shown). Please reopen if you still see the problem.