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

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.

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

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.

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

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?

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

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)

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.

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.

Yeah, agree...

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

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".

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 <email address hidden> Fri, 29 Apr 2016 14:38:53 -0700

I uploaded gnome-session to yakkety and xenial

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) <email address hidden> Thu, 12 May 2016 14:44:19 +0100

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!

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!

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 <email address hidden> Fri, 13 May 2016 09:14:24 +0100

The verification of the Stable Release Update for gnome-session has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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 <email address hidden> Thu, 19 May 2016 12:04:29 +0100