gnome-keyring-daemon not available in apps started from global shortcuts

Bug #755898 reported by Daniel Hahler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Debian)
Fix Released
Unknown
gnome-keyring (Ubuntu)
Fix Released
Low
Unassigned
gnome-session (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: gnome-control-center

When setting up a global shortcut via gnome-keybinding-properties (e.g. `gnome-terminal`), the application started from there will not have the environment set up to work with gnome-keyring-daemon ($SSH_AUTH_SOCK is missing).

When searching for it, I've found an older Debian bug about it (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339785):
  * 02_gsd-spawn.patch: spawn gnome-settings-daemon using g_spawn
     instead of DBus. Closes: #339785.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gnome-control-center 1:2.32.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 10 01:51:32 2011
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/zsh
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to natty on 2011-04-02 (7 days ago)

Revision history for this message
Daniel Hahler (blueyed) wrote :
Changed in gnome-control-center (Debian):
status: Unknown → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems fixed in Oneiric

affects: gnome-control-center (Ubuntu) → gnome-settings-daemon (Ubuntu)
affects: gnome-settings-daemon (Ubuntu) → gnome-session (Ubuntu)
Changed in gnome-session (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
Changed in gnome-keyring (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
Revision history for this message
Raphaël Halimi (raph) wrote :

I just installed Oneiric and this doesn't seem to be fixed (or maybe my problem is different).

The "Launch terminal" default keybinding, which launches gnome-terminal (this cannot be changed anymore, "Terminal" is now missing from the Default Applications settings, this is bad) indeed passes the right environment variables and thus uses gnome-keyring correctly.

On the other hand, if I define a new custom keybinding to launch XTerm, it's launched with the wrong environment variables and doesn't use gnome-keyring, asking for my ssh private key's passphrase everytime I want to login to a remote host.

Programs launched with the default keybindings and the ones launched with custom keybindings still end up with different environment variables, so the problem isn't fixed.

Revision history for this message
Raphaël Halimi (raph) wrote :

I just made a little test : I changed the value of /desktop/gnome/applications/terminal/exec in gconf from "gnome-terminal" to "xterm" and now xterm has the right settings.

So the real problem is indeed that default keybindings and custom ones are somewhat started differently by gnome (or its keybindings daemon) and this is not fixed yet in Oneiric.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.