After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 661642 - environment variables not passed through to programs launched via keyboard shortcuts
environment variables not passed through to programs launched via keyboard sh...
Status: RESOLVED DUPLICATE of bug 662528
Product: gnome-settings-daemon
Classification: Core
Component: general
3.0.x
Other Linux
: Normal major
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-10-13 09:56 UTC by Sam Morris
Modified: 2012-04-22 11:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sam Morris 2011-10-13 09:56:05 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.
Comment 1 Sam Morris 2011-10-13 13:40:22 UTC 
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.
Comment 2 Mantas Mikulėnas (grawity) 2012-03-14 22:33:40 UTC 
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.)
Comment 3 Sam Morris 2012-03-28 22:21:21 UTC 
(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.
Comment 4 Bastien Nocera 2012-03-29 11:11:30 UTC 
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 ***
Comment 5 m.spring 2012-04-20 16:07:43 UTC 
Confirmed here - and hindering productivity pretty much.
Comment 6 Bastien Nocera 2012-04-21 12:29:48 UTC 
(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.
Comment 7 m.spring 2012-04-22 11:44:55 UTC 
Sorry, that should have gone to 662528. In gnome 3.4 under ubuntu 11.10 it is still not working.