Bug 912161 - gnome-settings-daemon doesn't set its environment properly
Summary: gnome-settings-daemon doesn't set its environment properly
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-18 00:42 UTC by Andre Costa
Modified: 2014-02-05 19:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:15:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 693381 0 None None None Never

Description Andre Costa 2013-02-18 00:42:28 UTC
Description of problem:
While trying to gather data for bug 906745 I found out (with invaluable help from one of gnome-terminal developers) that the actual problem was not with gnome-terminal itself, but rather with gnome-settings-daemon. To cut a long story short, it's not setting its environment properly, which makes it use a different environment than the user's, and this leads to some things not working right (eg. launching gnome-terminal through a keyboard shortcut is *different* than launching it through alt+f2).

Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.6.4-3.fc18.x86_64

How reproducible: always


Steps to Reproduce:
1. write a script to output environment vars to a file and bind it to some keyboard shortcut (say, alt+e)
2. login to gnome-shell
3. press alt+e
4. backup the output file
5. run *the same script* through alt+f2
  
Actual results: environments are different


Expected results: the environment should be the same on both cases


Additional info: I'm using pt_BR locale for "formats" (LC_NUMERIC, LC_TIME, LC_MONETARY and LC_MEASUREMENT), and these (among others) are only set when the script is run through alt+f2. Please refer to bug filed upstream [https://bugzilla.gnome.org/show_bug.cgi?id=693381] for a detailed description with examples.

Comment 1 Fedora End Of Life 2013-12-21 11:30:00 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 2 Fedora End Of Life 2014-02-05 19:15:53 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.