Doing that produces b). The login keyring is there, but is locked. I was not aware that it was locked. I unlocked it, and the credentials are then displayed.

However, gnome-rdp fails to read the login information, write any new ones, and produces many errors (see attached).

Running seahorse again, shows the login keyring unlocked, but with no credentials stored anymore.

I see the bug report has been closed.



On Thu, 29 Apr 2010, Alexander Kurtz wrote:

Am Donnerstag, den 29.04.2010, 09:02 -0400 schrieb Sean McGuire:
2) upgraded to gnome-keyring and libgnome-keyring0 2.30.1-2 and then
ran seahorse without logging out or killing any daemons and the
passwords are not there.  See step2.png.

** (seahorse:2535): WARNING **: DNS-SD initialization failed: Daemon not running
** Message: init gpgme version 1.2.0

3) logged out, killed any gnome-keyring-daemon processes, logged back
in and ran seahorse.  No passwords were present.  Same screen capture
as step2.png.

** (seahorse:3209): WARNING **: DNS-SD initialization failed: Daemon not running
** Message: init gpgme version 1.2.0

Well in both cases everything seems to be fine. There seem to be no
g-k-d errors (as opposed to your first `seahorse.out' file) and
step2.png DOES show your login keyring, it's just not unlocked yet. You
can unlock it by right-clicking and then selecting unlock.

Could you please test what happens if you update everything, logout and
login again and then run seahorse on a terminal? Does it either

a) Show NO keyrings and complain both in the terminal an on the lower
  end of the window that it can't connect to g-k-d.
  (like in broken.{txt,png})
b) or show your login keyring (still locked?) and does not complain.
  (like in working-but-locked.{txt,png})
c) or something different. (What?)

Best Regards

Alexander Kurtz
Gnome.Keyring.KeyringException: Unknown error
  at Gnome.Keyring.Ring.FindNetworkPassword (System.String user, System.String 
domain, System.String server, System.String obj, System.String protocol, 
System.String authtype, Int32 port) [0x00000] 
  at GnomeRDP.KeyringProxy.GetPassword (System.String user, System.String 
domain, System.String server, Int32 protocol) [0x00000] 
Gnome.Keyring.KeyringException: Unknown error
  at Gnome.Keyring.Ring.FindNetworkPassword (System.String user, System.String 
domain, System.String server, System.String obj, System.String protocol, 
System.String authtype, Int32 port) [0x00000] 
  at GnomeRDP.KeyringProxy.GetPassword (System.String user, System.String 
domain, System.String server, Int32 protocol) [0x00000] 
Gnome.Keyring.KeyringException: Unknown error
  at Gnome.Keyring.Ring.FindNetworkPassword (System.String user, System.String 
domain, System.String server, System.String obj, System.String protocol, 
System.String authtype, Int32 port) [0x00000] 
  at GnomeRDP.KeyringProxy.GetPassword (System.String user, System.String 
domain, System.String server, Int32 protocol) [0x00000] 
Gnome.Keyring.KeyringException: Unknown error
  at Gnome.Keyring.Ring.FindNetworkPassword (System.String user, System.String 
domain, System.String server, System.String obj, System.String protocol, 
System.String authtype, Int32 port) [0x00000] 
  at GnomeRDP.KeyringProxy.GetPassword (System.String user, System.String 
domain, System.String server, Int32 protocol) [0x00000] 
Gnome.Keyring.KeyringException: Unknown error
  at Gnome.Keyring.Ring.FindNetworkPassword (System.String user, System.String 
domain, System.String server, System.String obj, System.String protocol, 
System.String authtype, Int32 port) [0x00000] 
  at GnomeRDP.KeyringProxy.GetPassword (System.String user, System.String 
domain, System.String server, Int32 protocol) [0x00000] 
Gnome.Keyring.KeyringException: Unknown error
  at Gnome.Keyring.Ring.FindNetworkPassword (System.String user, System.String 
domain, System.String server, System.String obj, System.String protocol, 
System.String authtype, Int32 port) [0x00000] 
  at GnomeRDP.KeyringProxy.GetPassword (System.String user, System.String 
domain, System.String server, Int32 protocol) [0x00000] 

Reply via email to