touch-packages team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

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