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
