Bug 682881

Summary:	g-s-d handled keybindings launch apps with incorrect environemt
Product:	[Fedora] Fedora	Reporter:	Mark McLoughlin <markmc>
Component:	gnome-settings-daemon	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	14	CC:	bnocera, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-16 12:28:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Mark McLoughlin 2011-03-07 21:06:48 UTC

(Bear with me hear, I'm woefully out of date)

For a long time now, I've had this keybinding:

  $> gconftool-2 -s /apps/metacity/keybinding_commands/command_1 -t string gnome-terminal
  $> gconftool-2 -s /apps/metacity/global_keybindings/run_command_1 -t string '<Alt>F3'

and it works fine, and it still works fine with Fedora 14

However, with a new account, I set this up through gnome-keybindings-properties and got totally confused as to why e.g. $SSH_AUTH_SOCK wasn't being set in the shell by gnome-keyring-daemon. The shell was also starting up in / instead of ~

If I delete the /desktop/gnome/keybindings entry for this and set it up for metacity to handle it using the GConf settings above, it works fine

What's the story here? Is it something like gnome-settings-daemon is launched before gnome-keyring-daemon and metacity is launched after it?

(It worked fine when it was launched by Bonobo ... why did ye have to go and break it?)

/me *ducks* :-P

Comment 1 Bastien Nocera 2011-03-10 18:54:38 UTC

The problem is that gnome-settings-daemon is launched by gnome-session, not later on, so it has no knowledge of the environment after being launched.

See https://bugzilla.gnome.org/show_bug.cgi?id=586825

Comment 2 Fedora End Of Life 2012-08-16 12:28:16 UTC

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping