Keyboard 'Custom Shortcut' does not retain environment

I tried another thing :
as, for me, gnome integrated launcher is a mess [no tab completion!!!!], I tried to use "gmrun", which is really faster, nicer and so on.
But I have exactly the same behavior using gmrun or shortcuts ! NO env, NO ssh-agent [for a sysadmin work, it's.... well, just imagine]...

that's really, really, REALLY annoying.

I see something interesting :
"env" command outputs some nice thing, especially :

[gnome-terminal launched through menu]
GNOME_KEYRING_SOCKET=/tmp/keyring-mNji2A/socket
SSH_AUTH_SOCK=/tmp/keyring-mNji2A/socket.ssh

[gnome-terminal launched through gmrun]
GNOME_KEYRING_SOCKET=/tmp/keyring-mNji2A/socket
SSH_AUTH_SOCK=/tmp/ssh-gvpqNC5125/agent.5125

shouldn't SSH_AUTH_SOCK be the same ?!
When launching a second terminal through the menu, it shows me that it's using the same agent [that's logical...]

so, question is : why is it using a second, unknown agent when it's launched through another mean ??

Are you aware that there is already a defined shortcut in the 'Desktop' section named 'Run a terminal'?

The behaviour describe does not occur when you map a shortcut to 'Run a terminal'

I can, however, confirm this behaviour for a new 'Custom Shortcut' launching a terminal program...

I am going to rename this bug and mark it as 'Confirmed'

I can confirm this behaviour

assigning to appropriate package and parties

the bug should be sent to the software writters on bugzilla.gnome.org

Hello,

I discovered this one a bit later after I opened the bug.
Fact is, when we use another launcher than the default one (which has no tab completion...) like gmrun, environment isn't kept as well... so it's not only for "custom shortcuts", and maybe it's the same problem source (gnome-setting-manager).

Thanks for your answers. Should I post it on bugs.gnome.org ?

Regards,

C.

opening the bug upstream would be nice indeed

opened upstream :
http://bugzilla.gnome.org/show_bug.cgi?id=582436 and linked to this one.

Thank you for sending the bug to GNOME

This is still happening in the latests lucid beta. Does it have something to do with the startup order that gdm is using?

still happening in the release version of lucid.

Here's a workaround: Using gconf-editor and editing the run_command_* and command_* in /apps/metacity/global_keybindings and /apps/metacity/keybinding_commands, respectively. Keyboard shortcuts created this way will start the applications with the correct environment.

By the way, it seems that the keyboard shortcuts from the "preferences" -> "keyboard shortcut" application are scattered across three different places in gconf: /apps/metacity/, /apps/gnome_settings_daemon/keybindings and /desktop/gnome/keybindings.