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 seahor
[ This time with cc'ing the bug report ]
Am Mittwoch, den 28.04.2010, 09:32 -0400 schrieb Sean McGuire:
> I did run that, but saw no difference. And no errors were thrown other
> than the same one as before:
>
> ** (seahorse:17351): WARNING **: DNS-SD initialization failed: Daemon not
> runnin
I did run that, but saw no difference. And no errors were thrown other
than the same one as before:
** (seahorse:17351): WARNING **: DNS-SD initialization failed: Daemon not
running
** Message: init gpgme version 1.2.0
Don't mean to be so troublesome,
Sean
On Tue, 27 Apr 2010, Alexander K
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm bitten by this bug too. I did everything advised in here but
seahorse is still unable to display my keyrings. Subsequently
telepathy-mission-control and empathy are not working right now as they
rely on gnome-keyring for their passwords.
> killall
Am Dienstag, den 27.04.2010, 12:14 -0400 schrieb Sean McGuire:
> After upgrading to 2.30-2 gnome-keyring, the passwords are gone. See
> attached 'seahorse.out' for the output from this. Running gnome-rdp
> now generates many errors (sorry, I usually don't run from a terminal,
> so I didn't not
With the downgraded gnome-keyring 2.28-2, seahorse shows passwords
stored for gnome-rdp under Passwords.
After upgrading to 2.30-2 gnome-keyring, the passwords are gone. See
attached 'seahorse.out' for the output from this. Running gnome-rdp
now generates many errors (sorry, I usually don't
Am Dienstag, den 27.04.2010, 09:10 -0400 schrieb Sean McGuire:
> Unfortunately I followed your fix and gnome-rdp is still not saving
> passwords. I logged out and even rebooted. Gconf has all three keys
> set. The gnome-keyring-daemon is running. I even tried manually ran
> all three command
What a great run-down. Thank you so much for investigating so
thoroughly.
Unfortunately I followed your fix and gnome-rdp is still not saving
passwords. I logged out and even rebooted. Gconf has all three keys
set. The gnome-keyring-daemon is running. I even tried manually ran
all three
Hi guys,
I ran into the same problem. Since this is going to be be a long mail, I
try to give you the most important things first:
Fixing the problem
==
You need to rebuild your gconf database. Run this as root:
gconf-schemas --register-all
Now start gconf-editor and check /a
Same here. Seahorse complains it can't connect to the gnome-keyring-daemon.
After killing gnome-keyring-daemon and starting it manually, I can create
new keyrings in seahorse again. Reverting to 2.28.2-1 helped here too. I use
GDM.
cheers,
--
Frank Hart
libgnome-keyring (2.30.0-2) unstable; urgency=low
Yes, I have logged out several times and rebooted. Still did not work.
I just downgraded to gnome-keyring_2.28.2-1_i386.deb and
libgnome-keyring0_2.28.2-1_i386.deb and gnome-rdp is able to save
passwords again.
Thank you for the quick respon
Le vendredi 16 avril 2010 à 08:47 -0400, Sean McGuire a écrit :
> Package: gnome-keyring
> Version: 2.30.0-2
> Severity: important
>
>
> After upgrading to gnome-keyring 2.30.0-2, gnome-rdp no longer saves
> or uses passwords for remote desktop logins. It was working prior to
> the upgrade.
Wha
Package: gnome-keyring
Version: 2.30.0-2
Severity: important
After upgrading to gnome-keyring 2.30.0-2, gnome-rdp no longer saves or uses
passwords for remote desktop logins. It was working prior to the upgrade.
I see that #577624 and #577627 report similarly, but for 2.30.0-1 and Evolution
a
13 matches
Mail list logo
