[Bug 809900] Re: Environment of alt-f2 commands not the same as compiz'

Launchpad Bug Tracker 809900 at bugs.launchpad.net
Wed Jul 13 16:00:32 UTC 2011


This bug was fixed in the package dbus - 1.4.12-4ubuntu2

---------------
dbus (1.4.12-4ubuntu2) oneiric; urgency=low

  * debian/dbus-Xession: revert debian's commit which changed the way the
    environment is updated for dbus-launch commands, the issue it fixes is
    rather marginal but it creates issues commands run using gio, which is
    the case of i.e indicators or unity "run a command" (lp: #807614, #809900)
 -- Sebastien Bacher <seb128 at ubuntu.com>   Wed, 13 Jul 2011 17:49:11 +0200

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

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

Title:
  Environment of alt-f2 commands not the same as compiz'

Status in Unity:
  Invalid
Status in “dbus” package in Ubuntu:
  Fix Released

Bug description:
  Hi

  I use the Xsession-launched ssh-agent for my Ubuntu sessions.  When
  launching a xterm with a keyboard shortcut of mine (alt-x) setup in
  GNOME -- probably same result as if you launch gnome-terminal with
  ctrl-shift-t), I see SSH_AGENT_PID and SSH_AUTH_SOCK in the env.
  However, if I run xterm from unity's alt-f2, I don't get these
  environment variables, wihch is problematic when running scripts from
  the alt-f2 prompt which use SSH.

  Thanks,

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




More information about the foundations-bugs mailing list