[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-26 Thread Chris Bainbridge
** Also affects: xfce4-session via http://bugzilla.xfce.org/show_bug.cgi?id=8014 Importance: Unknown Status: Unknown ** Also affects: xfce4-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, whi

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-26 Thread Chris Bainbridge
Another comment from Guido regarding modifying the /etc/ autostart files: "What happens is that if gnome-keyring components are not initialized through XDG autostart any more they will be DBus-activated (see https://live.gnome.org/GnomeKeyring/RunningDaemon). So when they start adding back the aut

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-26 Thread Chris Bainbridge
I was interested in the correct solution rather than the workaround of manually reverting the changes to gnome-keyring's /etc/ config. I asked Guido Berhoerster, and he said: "if you are not running gnome-session then gnome-keyring-daemon cannot be correctly initialized through the XDG autostart m

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-25 Thread Bug Watch Updater
Launchpad has imported 15 comments from the remote bug at https://bugzilla.novell.com/show_bug.cgi?id=710038. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://hel

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-25 Thread Chris Bainbridge
** Bug watch added: Novell/SUSE Bugzilla #710038 https://bugzilla.novell.com/show_bug.cgi?id=710038 ** Also affects: gnome-keyring (openSUSE) via https://bugzilla.novell.com/show_bug.cgi?id=710038 Importance: Unknown Status: Unknown -- You received this bug notification because y

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-25 Thread Bug Watch Updater
** Changed in: gnome-keyring Status: Unknown => Fix Released ** Changed in: gnome-keyring Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: WARNING

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-25 Thread Chris Bainbridge
** Bug watch added: GNOME Bug Tracker #660240 https://bugzilla.gnome.org/show_bug.cgi?id=660240 ** Also affects: gnome-keyring via https://bugzilla.gnome.org/show_bug.cgi?id=660240 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member

Re: [Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-16 Thread yitzhakbg
On Wed, 16 May 2012 12:17:36 - Ben Hearsum wrote: > The instructions in this forum post effectively worked around the issue > for me: http://ubuntuforums.org/showpost.php?p=10301640&postcount=8 > > -- > You received this bug notification because you are subscribed to the bug > report. > htt

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-16 Thread superxor
I've started facing this problem. I am using Ubuntu 12.04 with 'Awesome' window manager. Keeps appearing when I am trying to use Git to clone/push/pull. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/93

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-16 Thread Ben Hearsum
The instructions in this forum post effectively worked around the issue for me: http://ubuntuforums.org/showpost.php?p=10301640&postcount=8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932177 Title:

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-16 Thread Ben Hearsum
I just started hitting this in Ubuntu 12.04, running 'awesome'. When I try to launch gnome-setting-daemon I get: ➜ ~ gnome-settings-daemon WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-AASi0t/pkcs11: No such file or directory ** (process:1884): WARNING **: GDBus.Error:org.freedes

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-15 Thread Krishna E. Bera
Further to comment #5 above, i run Lubuntu 12.04 so i appended the string "LXDE;Lubuntu;" to the offending lines and the warning went away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932177 Title:

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-05-10 Thread Alvin
Running 12.04 w/ gnome-shell see this bug everytime I use git to clone a repository -- sometimes preventing the ability to do so it authentication is required happy to help anyone debug the issue -- competent with python haven't done much of anything with C have already tried removing and re-ins

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-04-30 Thread Unit 193
As found in one upstream bug, you can use a temporary fix/workaround for Xfce by doing sudo sed -i.bak 's/OnlyShowIn=GNOME;Unity;/OnlyShowIn=GNOME;Unity;XFCE;/g' /etc/xdg/autostart/gnome-keyring-*.desktop Then logging out and back in. -- You received this bug notification because you are a m

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-04-24 Thread Chris Bainbridge
** Bug watch added: Red Hat Bugzilla #783568 https://bugzilla.redhat.com/show_bug.cgi?id=783568 ** Also affects: gnome-keyring (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=783568 Importance: Unknown Status: Unknown -- You received this bug notification because you are

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-04-13 Thread Bug Watch Updater
** Changed in: gnome-keyring (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: WARNING: gnome-keyring:: couldn't connect to PKCS11 To manage notific

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-04-13 Thread Chris Bainbridge
** Bug watch added: Debian Bug tracker #653011 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653011 ** Also affects: gnome-keyring (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653011 Importance: Unknown Status: Unknown -- You received this bug notification bec

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-04-10 Thread Ulf Rehmann
For me, the problem does occur for movemail in emacs since an upgrade to precise last night: movemail: gnome-keyring:: couldn't connect to: /tmp/keyring- dq8XqX/pkcs11: No such file or directory System: Ubuntu 12.04 Packages: dpkg -l | grep gnome-keyring ii gnome-keyring

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-04-05 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/932177 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-03-04 Thread Launchpad Bug Tracker
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/932177 Title:

[Bug 932177] Re: WARNING: gnome-keyring:: couldn't connect to PKCS11

2012-02-14 Thread Paul Bogmat
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: WARNING: gnome-keyring:: couldn't connect to PKCS11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sourc