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

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.13.2-0ubuntu21.1

---
upstart (1.13.2-0ubuntu21.1) xenial; urgency=medium

  * Cherry-pick upstream fixes to publish global session variable changes
to the dbus environment. LP: #1433013.

 -- Dimitri John Ledkov   Thu, 19 May 2016 12:04:29
+0100

** Changed in: upstart (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Released
Status in upstart source package in Xenial:
  Fix Released

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session -
3.18.1.2-1ubuntu1.16.04.1

---
gnome-session (3.18.1.2-1ubuntu1.16.04.1) xenial; urgency=medium

  [ Iain Lane ]
  * Update Vcs-Bzr for 16.04

  [ Marco Trevisan (Treviño) ]
  * debian/patches/export_env_to_upstart.patch:
- Export environment variables to upstart as well, if available (LP: 
#1433013)

 -- Iain Lane   Fri, 13 May 2016 09:14:24 +0100

** Changed in: gnome-session (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Released
Status in upstart source package in Xenial:
  Fix Committed

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Treviño]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Committed
Status in upstart source package in Xenial:
  Fix Committed

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

Hello Dimitri, or anyone else affected,

Accepted upstart into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upstart/1.13.2-0ubuntu21.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: upstart (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Committed
Status in upstart source package in Xenial:
  Fix Committed

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/upstart/xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Committed
Status in upstart source package in Xenial:
  In Progress

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

** Changed in: upstart (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: upstart (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Committed
Status in upstart source package in Xenial:
  In Progress

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Treviño]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Committed
Status in upstart source package in Xenial:
  New

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

Hello Dimitri, or anyone else affected,

Accepted gnome-session into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
session/3.18.1.2-1ubuntu1.16.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: upstart (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

** Changed in: gnome-session (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Committed
Status in upstart source package in Xenial:
  New

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Treviño]

** Tags added: desktop-trello-import

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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
Status in gnome-session source package in Xenial:
  In Progress
Status in upstart source package in Xenial:
  New

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.18.1.2-1ubuntu2

---
gnome-session (3.18.1.2-1ubuntu2) yakkety; urgency=medium

  * debian/patches/export_env_to_upstart.patch:
- Export environment variables to upstart as well, if available (LP: 
#1433013)

 -- Marco Trevisan (Treviño)   Thu, 12 May 2016
14:44:19 +0100

** Changed in: gnome-session (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Released
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
Status in gnome-session source package in Xenial:
  In Progress
Status in upstart source package in Xenial:
  New

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Committed
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
Status in gnome-session source package in Xenial:
  In Progress
Status in upstart source package in Xenial:
  New

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Iain Lane]

I uploaded gnome-session to yakkety and xenial

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

** Also affects: upstart (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Fix Committed
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
Status in gnome-session source package in Xenial:
  In Progress
Status in upstart source package in Xenial:
  New

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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Treviño]

** 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-/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-/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
Touch seeded packages, 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-/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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.13.2-0ubuntu23

---
upstart (1.13.2-0ubuntu23) yakkety; urgency=medium

  * Cherry-pick upstream fix to publish global session variable changes to
the dbus environment.  LP: #1433013.

 -- Steve Langasek   Fri, 29 Apr 2016
14:38:53 -0700

** Changed in: upstart (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 upstart package in Ubuntu:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/gnome-session/upstart-export-variables

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 upstart package in Ubuntu:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 upstart package in Ubuntu:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Rolf Leggewie]

utopic has seen the end of its life and is no longer receiving any
updates. Marking the utopic task for this ticket as "Won't Fix".

** Changed in: upstart (Ubuntu Utopic)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 upstart package in Ubuntu:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Mathew Hodson]

** No longer affects: unity-lens-applications (Ubuntu)

** Project changed: unity => ubuntu-translations

** No longer affects: ubuntu-translations

** No longer affects: unity (Ubuntu)

** Changed in: upstart (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu Utopic)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu Vivid)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Iain Lane]

** Branch linked: lp:~laney/upstart/lp1433013

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Brian Murray]

** Tags removed: rls-w-incoming
** Tags added: rls-w-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Iain Lane]

I think it makes sense. DBus in wily (>= 1.9) does similar for
Xsession.d managed sessions:

# unset login-session-specifics
unset XDG_SEAT
unset XDG_SESSION_ID
unset XDG_VTNR

# tell dbus-daemon --session (and systemd --user, if running)
# to put the Xsession's environment in activated services'
# environments
dbus-update-activation-environment --verbose --systemd --all

You probably want to blacklist those same variables.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Treviño]

Yeah, agree...

The fix works, but having some blacklist of variables would be nice.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Will Cooke]

** Tags added: rls-w-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

There is untested patch attached as a merge proposal here.
In essence the environment variables should be uploaded into the dbus 
activation environment, such that when unity launcher is dbus activated, it can 
launch things with same variables as the upstart jobs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[ltsampros]

Is there any update on this issue? Is there any remedy or workaround
since alt-f2 is widely used?

(After all the ssh-agent/gnome-keyring trouble this is pretty
embarrassing)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: upstart (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: upstart (Ubuntu Vivid)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: upstart (Ubuntu Utopic)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ilya Murav'jov]

*ssh-agent doesn't work because set | grep SSH is empty.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: upstart (Ubuntu Trusty)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Ilya Murav'jov]

Hi,

I use Trusty, use Alt-f2 to start konsole. And ssh-agent doesn't run because 
set | grep SSH is empty.
Is there a workaround for this issue?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
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 proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Treviño]

** No longer affects: unity-lens-applications (Ubuntu Trusty)

** No longer affects: unity-lens-applications (Ubuntu Utopic)

** No longer affects: unity-lens-applications (Ubuntu Vivid)

** Changed in: unity-lens-applications (Ubuntu)
   Status: New = Won't Fix

** No longer affects: unity (Ubuntu Trusty)

** No longer affects: unity (Ubuntu Utopic)

** No longer affects: unity (Ubuntu Vivid)

** Changed in: unity (Ubuntu)
   Status: New = Won't Fix

** Changed in: unity
   Status: New = Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  New
Status in upstart source package in Trusty:
  New
Status in upstart source package in Utopic:
  New
Status in upstart source package in Vivid:
  New

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

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/upstart/lp1433013

** Branch linked: lp:~xnox/ubuntu/wily/upstart/lp1433013

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity-lens-applications source package in Trusty:
  New
Status in upstart source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity-lens-applications source package in Utopic:
  New
Status in upstart source package in Utopic:
  New
Status in unity source package in Vivid:
  New
Status in unity-lens-applications source package in Vivid:
  New
Status in upstart source package in Vivid:
  New

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

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

The branches attached solve this for me. I hope somebody from upstart
team can review them.

I'll try to put a ppa out with that patch in, such that other users that
are affected can also test this.

I expect to SRU this change to all stable releases.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity-lens-applications source package in Trusty:
  New
Status in upstart source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity-lens-applications source package in Utopic:
  New
Status in upstart source package in Utopic:
  New
Status in unity source package in Vivid:
  New
Status in unity-lens-applications source package in Vivid:
  New
Status in upstart source package in Vivid:
  New

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

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Iain Lane]

Can you please test this with the gnome-session in vivid-proposed /
wily? We think it might be the same issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity-lens-applications source package in Trusty:
  New
Status in upstart source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity-lens-applications source package in Utopic:
  New
Status in upstart source package in Utopic:
  New
Status in unity source package in Vivid:
  New
Status in unity-lens-applications source package in Vivid:
  New
Status in upstart source package in Vivid:
  New

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

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Brian Murray]

** Changed in: upstart (Ubuntu)
   Importance: Undecided = Medium

** Changed in: unity-lens-applications (Ubuntu)
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity-lens-applications source package in Trusty:
  New
Status in upstart source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity-lens-applications source package in Utopic:
  New
Status in upstart source package in Utopic:
  New
Status in unity source package in Vivid:
  New
Status in unity-lens-applications source package in Vivid:
  New
Status in upstart source package in Vivid:
  New

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

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1433013/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Dimitri John Ledkov]

So further experimentation revealed that we should be keeping the DBUS
activation environment up to date with all the initctl set-env calls.

Thus initctl set-env calls should call into
org.freedesktop.DBus.UpdateActivationEnvironment in the user session
upstart case.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1433013

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

Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity-lens-applications source package in Trusty:
  New
Status in upstart source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity-lens-applications source package in Utopic:
  New
Status in upstart source package in Utopic:
  New
Status in unity source package in Vivid:
  New
Status in unity-lens-applications source package in Vivid:
  New
Status in upstart source package in Vivid:
  New

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

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

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

  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp