From owner-freebsd-ports@FreeBSD.ORG Tue Apr 14 03:20:21 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE988106566B; Tue, 14 Apr 2009 03:20:21 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by mx1.freebsd.org (Postfix) with ESMTP id C4C7D8FC13; Tue, 14 Apr 2009 03:20:20 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by fxm11 with SMTP id 11so2263495fxm.43 for ; Mon, 13 Apr 2009 20:20:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6QTNe6E9u6Y0hd2NFMxI8064bRP2GRkAJFx7kCif6Ro=; b=RHouj9E8vh0SHfADN3I/De7/G0jbv+eoR+9LBZrLsYCcN0fELVQWddthStIUujP77d wZ6ppNCB7tRh0TGpkpaz22CaD+MIw7rJyULse9CRJz6Ao/h0QKSD8xElI6084VRHEfpW qHG3Fazcw7VohpuaYwamDkPJg2uCbeiiaxUEI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=EAjslkb746/VzUswzzH+aFN3GE+pAByhsaWnqyssOtYJf4Uc+Mfy3fiFy3SKsn9Ogo irEpNuxUYBLahEOLldTCQ0qXEpS0adHwy6h+mvMzi/uzrloP8A4tdgMVzKygWcTrWtNL hqTHWmk/65qPxiv2Haqh1noLLX/nBDZLD/04k= MIME-Version: 1.0 Received: by 10.223.107.19 with SMTP id z19mr1874308fao.27.1239677467907; Mon, 13 Apr 2009 19:51:07 -0700 (PDT) In-Reply-To: References: <1239343955.4933.113.camel@shumai.marcuscom.com> <1239667718.1304.66.camel@shumai.marcuscom.com> <1239669463.1304.67.camel@shumai.marcuscom.com> <1239670126.1304.75.camel@shumai.marcuscom.com> Date: Tue, 14 Apr 2009 04:51:07 +0200 Message-ID: <3f1fd1ea0904131951u5e6b211dlbb55af484d91e63b@mail.gmail.com> From: Michal Varga To: Dmitry Morozovsky Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: gnome@freebsd.org, ports@freebsd.org, Joe Marcus Clarke Subject: Re: HEADS UP: GNOME 2.26 available for FreeBSD X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2009 03:20:22 -0000 On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote: > Dear Joe Marcus, > > DM> JMC> What versions of gnome-keyring and seahorse do you have? > DM> > DM> marck@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' > DM> gnome-keyring-2.26.0 A program that keeps passwords and other secrets > DM> seahorse-2.26.0 =C2=A0 =C2=A0 GNOME application for managing encrypti= on keys (PGP, SSH) > > After > > portupgrade -f seahorse gnome-keyring > > and reboot > > still the same effect... > > Of course, I can wipe packages installed and set it up from scratch, but = I > would prefer a bit safer way if at all possible ;-) > Well, I have no idea what a "Terminal remote login" in this particular context is, so this may not be of any help, but I've seen this issue before: "Before the upgrade, I had once pop-up asking for my key passphrase, then let me use this private key during my (home) session without further asking= .. Now, when I try to connect to the host which even possibly want to check whether I want to present some key there, I got the pop-up. I even checked = that I can connect to the host in question using plain xterm, and have usual password qiery." I've been in similiar situation some time ago, when new gnome-keyring/seahorse (it started with one of the recent versions, don't remember exactly when, but definitely before 2.26 was introduced) for some surely interesting reason insisted on creating a very own keyring every other reboot - while originally you were using one default keyring (let's call it "default") for storing your passwords, now gnome-keyring kept creating a new one named "login" and always set it as the default one. That "login" keyring was even more special in that that nothing stored in it ever worked, it still kept asking for passwords and even then was not able to use them (and lost them on the next reboot anyway.. Maybe that's a feature, don't know, don't care). I've run into this on a few different machines, every time I needed to open 'seahorse', get to Passwords tab, delete the "login" keyring, set the original "default" as the default keyring (first time I wiped them all and created a clean one to be sure, but as it turned out later, this wasn't needed), after that, passwords worked fine again. This procedure again and again for a few days/reboots, until seahorse miraculously stopped this madness and let my default keyring be, well, default (yes, just like that). Anyway, if you weren't there yet, check seahorse gui for what keyring are you really using, maybe you've hit the same issue with the "login" stupidity.. m.