*** This bug is a duplicate of bug 932177 ***
https://bugs.launchpad.net/bugs/932177
** This bug has been marked a duplicate of bug 932177
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
--
You received
** Changed in: gnome-keyring
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
https://bugs.launchpad.net/bugs/569667
Title:
Error communicating with gnome-keyring-daemon
--
** Changed in: gnome-keyring
Importance: Unknown = Medium
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
You comment on a closed bug, you should rather open a new one if you
want people to read your comments. If a password is requires it's normal
it's asking for one on login since it can't guess it for you or the
storage would be unsecure...
--
Error communicating with gnome-keyring-daemon
I'm not sure I'm reading this bug system's UI properly, but it looks
like this is still open (New not Invalid) as regards the GNOME
keyring subsystem, and that's where the upstream bug is being tracked.
This bug is closed (Invalid) with respect to the subsystem gnome-
keyring (ubuntu) but it's
I'm currently using maverick and here i use auto login at boot but did not
disabled the login windows after log off i would it a try and see if the bug
with empathy and the keyring still exist here and if not then maybe this bug
report could be close as long as
it doesn't happen to anyone
Problem still exist i just tried and got the same message at the bottom
of seashore can't communicating with gnome-keyring-daemon or Error
communicating with gnome-keyring-daemon i'm translating it from Hebrew
so it might not be accurate.
And also empathy doesn't work well at all there are no
Upstream, the GNOME bug 616861 has very little data and no triage or
assignment, certainly nothing like Forest's excellent analysis that
appears here comment 18 and in bug 357346, plus whatever notes he has
put in the bugs linked to from there.
This seems insane. Would it get more attention to
I recently upgraded from Xubuntu Karmic to Lucid, and ran into the same
error: both nm-applet and seahorse were failing to contact gnome-
keyring-daemon. After a lot of investigation, I'm starting to think I
know what's going on:
- Seahorse, nm-applet, and probably a lot of other components
This problem is related to a user being password-less(as set in Users
and Groups). On a newly installed 10.04 system I had to disable
password-less mode to get Seahorse to be able to connect to the gnome-
keyring-daemon.
@Michal: gnome-keyring-daemon --start --components=pkcs11 is the
default for
The user is not password-less the user have a password i only chosed
auto login during the install process via ubiquity and the it something
that you can also change via login screen option in system-
administrative or preference i don't remember right now but the problem
for me at least don't
I discovered that if don't disable the need to enter password when you
log off then everything is ok but your solution is also a good one.:)
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of
I had the same problem and found following solution:
1. Go to System - Preferences - Startup Applicataions
2. Find Item: Certificate and Key Storage and edit it
3. Change command to: gnome-keyring-daemon and save it.
4. Reboot
NOTE: After upgrade from 9.10, there was following command: gnome-
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Package changed: seahorse (Ubuntu) = gnome-keyring (Ubuntu)
** Changed in:
This site is a mess i have an account there and i can't log in i ever
restored the password twice and i still can't log in so it want be me i
guess.
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member
https://bugzilla.gnome.org/post_bug.cgi
** Bug watch added: GNOME Bug Tracker #616861
https://bugzilla.gnome.org/show_bug.cgi?id=616861
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of
https://bugzilla.gnome.org/show_bug.cgi?id=616861
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs mailing
I am sorry fo the post above - it turned out to be a problem with my home
folder - I reinstalled again yesterday and transferred only the crucial folders
and setting one by one; now everything is working like a charm. The fact
remains though that this happened after an update, I have no idea
thank you for sending the bug to GNOME
** Changed in: gnome-keyring (Ubuntu)
Status: New = Triaged
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=616861
Importance: Unknown
Status: Unknown
--
Error communicating with gnome-keyring-daemon
** Changed in: gnome-keyring
Status: Unknown = New
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs
We need more information upstream. Reporting the bug there is one thing,
but making the report clear is another. There's no point in making a
copy/paste of the symptoms reported in Launchpad: upstream needs
something detailed enough. Would somebody that understands the causes of
the problem
ok, let's close the bug then, you might want to close the GNOME one too
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = Invalid
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of
is there any more information i can provide from my ubuntu machine?
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/45289218/Dependencies.txt
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The only way i know to reproduce this problem is by restarting Ubuntu
because one time is working fine and the other is not it as simple as
this.
--
Error communicating with gnome-keyring-daemon
https://bugs.launchpad.net/bugs/569667
You received this bug notification because you are a member of
When i check now I'm starting to think it's more users-admin problem and not
seahorse in users-admin there is an option asked on login and don't asked on
login i think if i use the letter this cause the problem i mentioned i think
so because i just logged of
and logged on with this option on
The same problem here, but I think this is a wider problem, too - the RC
(specifically speaking - the updates after RC) really rendered my computer
useless:
1. I have to enter all the passwords for everything all over again (I get the
communication with keyring error)
2. neither nm-applet nor
27 matches
Mail list logo
