After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 669171 - WARNING: gnome-keyring:: no socket to connect to
WARNING: gnome-keyring:: no socket to connect to
Status: RESOLVED DUPLICATE of bug 665961
Product: gnome-keyring
Classification: Core
Component: general
3.2.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-02-01 13:19 UTC by Michael Basse
Modified: 2012-02-01 13:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Basse 2012-02-01 13:19:01 UTC 
the latest dist-upgrade on 12.04 (10.01.12) gives a WARNING about gnome-keyring

WARNING: gnome-keyring:: no socket to connect to

I will put some comments on our Lauchpad-Bug here:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/914305

---

01/11/12 10:09:50 PM jerry-Aspire-7739 gnome-keyring-daemon[2165] couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files
01/11/12 10:09:50 PM jerry-Aspire-7739 gnome-keyring-daemon[2165] unsupported key algorithm in certificate: 1.2.840.10045.
---

I'm trying to use aiccu (SixXS) and the daemon won't start because of the same bug. This means no IPv6 connectivity for me.
---

I also want to mention that this appears to be related to upstream Debian bug #649408, and breaks both network services and applications.


---
cups is no longer working

# lpq
WARNING: gnome-keyring:: no socket to connect to
Comment 1 Stef Walter 2012-02-01 13:23:43 UTC 

*** This bug has been marked as a duplicate of bug 665961 ***