Running Kubuntu 12.04 here, and I'd like to add that the gnome keyring bug(s)
also affects Mysql-Workbench, as its absxence means passwords aren't remembered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I discovered this bug today after installing elinks into a Kubuntu 13.04
system. Apparently elinks wants to access the keyring. It does not
keep the program from loading or working, but it does throw a warning
every time the program is opened from the command prompt.
--
You received this bug
** Bug watch added: Debian Bug tracker #649408
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408
** Also affects: gnome-keyring (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: gnome-keyring (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04] WARNING: gnome-keyring:: no socket to connect to
To
is that still an issue in precise (the Debian bug indicates it should be
fixed in the current version)
what desktop environment do people have the issue use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Sebastian,
its still affecting me on Lubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04] WARNING: gnome-keyring:: no socket to connect to
To manage notifications
I just performed a full update of all packages on my 12.04 installation,
rebooted, and tried again:
-
# lpq
WARNING: gnome-keyring:: no socket to connect to
mfc is ready
no entries
-
So the warning is still there. This installation was a regular install
with the Gnome 2 desktop
The issue you are reporting is an upstream one and it would be nice if
somebody having it could send the bug to the developers of the software
by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the
Upstreambug created https://bugzilla.gnome.org/show_bug.cgi?id=669171
and added into bugwatch
** Bug watch added: GNOME Bug Tracker #669171
https://bugzilla.gnome.org/show_bug.cgi?id=669171
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=669171
Importance:
already fixed upstream
https://bugzilla.gnome.org/show_bug.cgi?id=665961
commit 5ca7387952f99bf318d337df2d853f5bc3c0ddd2
Author: Stef Walter st...@collabora.co.uk
Date: Mon Dec 19 13:08:51 2011 +0100
rpc-layer: Correctly handle case where gnome-keyring-daemon not
running
* In the
Thanks, bringing issues to people who write the code works usually
better than discussing them for ages on distribution trackers
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: gnome-keyring
Status: Unknown = Invalid
** Changed in: gnome-keyring
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04]
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04] WARNING: gnome-keyring:: no socket to connect to
This bug was fixed in the package gnome-keyring - 3.2.2-2ubuntu1
---
gnome-keyring (3.2.2-2ubuntu1) precise; urgency=low
* Synchronizing on Debian including fix for 'gnome-keyring:: no socket to
connect to errors in non GNOME sessions' (lp: #914305)
-- Sebastien Bacher
I want to mention that the workaround listed in comment #6, involving
commenting out the module, does indeed work over here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04]
I also want to mention that this appears to be related to upstream
Debian bug #649408, and breaks both network services and applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
I think somebody who has access to do so should raise the priority of
this bug to a higher level. This bug has been known to break certain
network services, even services which have no apparent legitimate need
to be using gnome-keyring at all. It would be best if this bug were
fixed prior to the
I just wanted to add one example of a critical network service which is
broken by this bug, to demonstrate the broken functionality. CUPS
appears to be broken by this bug. I cannot print, and when I look in my
CUPS error log I see a bunch of messages about the daemon having
problems connecting
I can confirm what Brian is saying.
Evolution is also broken because it cant use gnome-keyring and asking
always for a password. Also cups is not working here
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Brian, can you please test the workaround from comment #6?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04] WARNING: gnome-keyring:: no socket to connect to
To manage
Edited this file: /etc/pkcs11/modules/gnome-keyring-module
and commented this line:
module: gnome-keyring-pkcs11.so
and the problem is gone for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Furthermore, I noticed the p11-kit package was NOT installed in my system,
which I suspect is required by gnome-keyring.
I installed it and reverted the /etc/pkcs11/modules/gnome-keyring-module to its
original state but the bug appeared again.
--
You received this bug notification because you
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'm also running Ubuntu 12.04 fully updated ten minutes ago.
Package: gnome-keyring
Priority: optional
Section: gnome
Installed-Size: 4184
Maintainer: Ubuntu Developers
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
I am running Kubuntu 12.04 fully updates as of 10:50PM tonight,
01/11/12.
I have the same warning, but it is also followed by
(BibleTime 2.8.1) WARNING: Not a BibleTime Bookmark XML file
Segmentation fault (core dumped)
Total removal and reinstall doesn't help.
--
You received this bug
I forgot to add these lines from my authentication log:
01/11/12 10:09:50 PMjerry-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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04] WARNING: gnome-keyring:: no socket to connect to
To manage notifications about this bug go to:
27 matches
Mail list logo
