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 mechanism because the
necessary environment variables cannot be set for your session (see my
detailed explanation at
https://bugzilla.novell.com/show_bug.cgi?id=710038#c2). So what that
basically means is that whether you initialize gnome-keyring through XDG
autostart or not does not make any difference outside GNOME because it
will be inaccessible from your session.

In order to use gnome-keyring with Xfce you need to enable "GNOME
compatibility mode", if you use something else you need to modify your
session wrapper so that it calls "gnome-keyring-daemon --start", reads
its output and exports the printed environment variables. That assumes
of course that gnome-keyring-daemon has been correctly started and
unlocked via PAM.

...starting with openSUSE 12.2 gnome-keyring will be installed and
enabled by default. It is also possible to use gnome-keyring with Xfce
on openSUSE 12.1 since we patch xfce4-session to avoid undesirable side
effects of GNOME compat mode in Xfce 4.8
(https://bugzilla.xfce.org/show_bug.cgi?id=8014#c0), however GNOME
compatibility mode needs to be enabled manually.

Making it work is relatively simple starting with Xfce 4.10 you just
need to follow https://live.gnome.org/GnomeKeyring/Pam and enable GNOME
compat mode.

For Xfce 4.8 it is more complicated because xfce4-session would need to
be patched with backports of commit
0fea8c64bfc32915d9e397e7029de150167a737d and
67b772364c9e9a7ea9cc4dafb219902c6c8b074a in order to make GNOME compat
mode usable."

** Bug watch added: Xfce Bugzilla #8014
   http://bugzilla.xfce.org/show_bug.cgi?id=8014

-- 
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:
  WARNING: gnome-keyring:: couldn't connect to PKCS11

Status in GNOME keyring services:
  Fix Released
Status in “gnome-keyring” package in Ubuntu:
  Confirmed
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