[Bug 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment

Marco Trevisan (Treviño) mail at 3v1n0.net
Thu May 12 14:36:27 UTC 2016


** Description changed:

  upstart in user session manages environmental variables and most things
- have them, however Alt-f2 started proccesses lack them.
+ have them, however Alt-f2 started processes lack them.
  
- to test
+ [Impact]
+ Some environment variables are missing from apps that are launcher from Alt+f2 command lens, or in general with dbus-activation (an example might be gnome-terminal, global menu not working).
  
+ [Test case]
  Super Key -> "xterm" -> Enter -> env | grep SSH
  
- vs
+ it should return something like:
+ SSH_AUTH_SOCK=/run/user/$UID/keyring-<random-stuff>/ssh
  
  Alt+F2 -> "xterm" -> Enter -> env | grep SSH
  
- via Super Key -> the environment is correct
+ The returned values should match the results got from the xterm instance
+ that has been ran from unity dash application lens (the one opened with
+ Super).
  
- via Alt-F2 -> it is not
+ The same should be checked for the variable XDG_MENU_PREFIX
  
+ Before this fix happened we had this result:
+   via Super Key -> the environment is correct
+   via Alt-F2 -> it is not
  
- I believe Alt+F2 code path should call into upstart dbus api to "list-env" and import that environment before executing the search result.
+ [Regression potential]

** Description changed:

  upstart in user session manages environmental variables and most things
  have them, however Alt-f2 started processes lack them.
  
  [Impact]
  Some environment variables are missing from apps that are launcher from Alt+f2 command lens, or in general with dbus-activation (an example might be gnome-terminal, global menu not working).
  
  [Test case]
  Super Key -> "xterm" -> Enter -> env | grep SSH
  
  it should return something like:
  SSH_AUTH_SOCK=/run/user/$UID/keyring-<random-stuff>/ssh
  
  Alt+F2 -> "xterm" -> Enter -> env | grep SSH
  
  The returned values should match the results got from the xterm instance
  that has been ran from unity dash application lens (the one opened with
  Super).
  
  The same should be checked for the variable XDG_MENU_PREFIX
  
  Before this fix happened we had this result:
-   via Super Key -> the environment is correct
-   via Alt-F2 -> it is not
+   via Super Key -> the environment is correct
+   via Alt-F2 -> it is not
  
  [Regression potential]
+ 
+ Nothing known. Some variables could be overridden, but this is expected.

** Also affects: gnome-session (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: gnome-session (Ubuntu)
       Status: New => In Progress

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-session (Ubuntu)
     Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in gnome-session package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Confirmed

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started processes lack them.

  [Impact]
  Some environment variables are missing from apps that are launcher from Alt+f2 command lens, or in general with dbus-activation (an example might be gnome-terminal, global menu not working).

  [Test case]
  Super Key -> "xterm" -> Enter -> env | grep SSH

  it should return something like:
  SSH_AUTH_SOCK=/run/user/$UID/keyring-<random-stuff>/ssh

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  The returned values should match the results got from the xterm
  instance that has been ran from unity dash application lens (the one
  opened with Super).

  The same should be checked for the variable XDG_MENU_PREFIX

  Before this fix happened we had this result:
    via Super Key -> the environment is correct
    via Alt-F2 -> it is not

  [Regression potential]

  Nothing known. Some variables could be overridden, but this is
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1433013/+subscriptions



More information about the foundations-bugs mailing list