(In reply to comment #14)
> Fixed in Factory.

it's back again in 12.3-RC1 (or never got fixed?) !

I'm using 12.3-RC1 plus updates and run XFCE4.

    /usr/bin/gnome-keyring-daemon --daemonize --login

gets started and it's loading offering all my ssh-keys, which is a no-
go!

when debugging my ssh-agent problems, I found the hint in some
discussions to rename/remove nome-keyring-daemon (or remove execute
permission).

this worked fine for me -- until bug #805048: 
NetworkManager needs gnome-keyring-daemon to ask for wifi passphrases :-((

so gnome-keyring-daemon is back in businees, and trashes my ssh usage:-(

looking for other solutions I found e.g.
http://ubuntuforums.org/showthread.php?t=1655397

but

     sudo gconftool-2 --direct --config-source 
xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set 
/apps/gnome-keyring/daemon-components/ssh FALSE
does not help.


https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/932177/comments/20

does not work either for me, the key daemon still loads/offers all ssh
keys (output of "ssh-add -l").


for now I've hacked the gnome-keyring-daemon to garble the path to my keys:

diff <( strings /usr/bin/gnome-keyring-daemon~ )  <( strings 
/usr/bin/gnome-keyring-daemon ) 
9543c9543
< ~/.ssh
---
> ~/@ssh


but of corse that's not the way to go:-(


so my question for running XFCE4:

how can I disable the ssh-agent functionality for gnome-keyring-daemon
these days ???


thanks for the real[tm] solution!!!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177

Title:
  XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
  correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

Status in GNOME keyring services:
  Fix Released
Status in Xfce4 session manager:
  Unknown
Status in “gnome-keyring” package in Ubuntu:
  Invalid
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “gnome-keyring” package in Debian:
  New
Status in “gnome-keyring” package in Fedora:
  Unknown
Status in “gnome-keyring” package in openSUSE:
  Fix Released

Bug description:
  precise + fluxbox (without gnome-settings-daemon) Postler when sending
  a message writes:

  Failed to send a message
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-rof1VB/pkcs11: No 
such file or directory

  In gnome-system-monitor:
  /usr/bin/gnome-keyring-demon --start --foreground --components=secrets
  /usr/bin/gnome-keyring-demon --daemonize --login

  with manual start this: OK
  /usr/bin/gnome-keyring-daemon --start --components=pkcs11

  Is it possible to add a string key '--components=pkcs11', so that the 
gnome-system-monitor was:
  /usr/bin/gnome-keyring-demon --start --foreground --components=secrets 
--components=pkcs11

  thanks in advance...

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-keyring 3.2.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.0-15-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 14 17:47:35 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to precise on 2012-02-10 (3 days ago)
  mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 
2012-02-14T14:17:23.632015
  mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: 
2012-02-14T14:17:23.632015
  mtime.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop: 
2012-02-14T14:17:23.632015
  mtime.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop: 
2012-02-14T14:17:23.636015

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/932177/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to