GNOME Bugzilla – Bug 661642
environment variables not passed through to programs launched via keyboard shortcuts
Last modified: 2012-04-22 11:44:55 UTC
1. log into GNOME
2. launch gnome-terminal from gnome-shell
3. observe gnome-keyring's environment variables in the environment (GPG_AGENT_INFO, SSH_AUTH_SOCK)
4. quit gnome-terminal
5. go to System Settings → Keyboard → Shortcuts → Custom Shortcuts
6. add a shortcut that launches gnome-terminal
7. trigger the shortcut
8. observe gnome-keyring's environment variables missing in the environment!
I doubt this is actually a gnome-keyring bug, but I don't know whether to file the bug against gnome-session, metacity, gnome-shell, etc.
Oops, meant to file this against gnome-settings-daemon since it's the process that appears to fork and exec gnome-terminal in reaction to me triggering the keyboard shortcut.
Still happens in 3.3.x, and has become much more annoying since a custom shortcut is now the only way to launch a terminal from keyboard. (3.2 had a built-in "Launch Terminal" shortcut, which was not affected by this.)
(In reply to comment #2)
> Still happens in 3.3.x, and has become much more annoying since a custom
> shortcut is now the only way to launch a terminal from keyboard. (3.2 had a
> built-in "Launch Terminal" shortcut, which was not affected by this.)
That makes the impact of this bug way more severe.
The other bug has patches and discussion.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.
*** This bug has been marked as a duplicate of bug 662528 ***
Confirmed here - and hindering productivity pretty much.
(In reply to comment #5)
> Confirmed here - and hindering productivity pretty much.
Confirmed what? This bug is closed as a duplicate, and the duplicate has been fixed.
Sorry, that should have gone to 662528. In gnome 3.4 under ubuntu 11.10 it is still not working.