X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 From: "Yaakov (Cygwin/X)" Date: Tue, 29 Nov 2011 21:19:10 -0600 Message-ID: Subject: gnome-keyring bug in snapshots To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com For some time now, snapshots have displayed a bug wrt gnome-keyring, namely that passwords don't "register" when entered. This wreaks havoc on the GNOME desktop where so many programs rely on gnome-keyring. This is easy to reproduce, but requires xorg-server, dbus, gnome-keyring, and openssh. At a new terminal: $ XWin -multiwindow &>/dev/null & $ export DISPLAY=:0 $ eval `dbus-launch --sh-syntax` $ export `gnome-keyring-daemon --start --components=ssh` $ ssh USER AT HOSTNAME (Enter password for ssh key in GUI prompt) What should happen (and does with 1.7.9) is a successful login. WIth the 20111129 snapshot, the following message is displayed on the terminal: Agent admitted failure to sign using the key. (which AFAIK comes from ssh) and the gnome-keyring prompt asks for the password to the next private key listed in ~/.ssh/config (even if its the wrong key for HOSTNAME). Subsequent logins do succeed, however. This does not occur with ssh-agent(1). Frankly, I'm a little baffled by this one, but a non-working GNOME desktop is really keeping me from testing the snapshots for any length of time. Yaakov Cygwin/X -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple