** Branch linked: lp:ubuntu/gnome-settings-daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program is
launched
To manage
** Package changed: gnome-session (Ubuntu) = gnome-settings-daemon
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how
This bug was fixed in the package gnome-settings-daemon - 3.4.0-0ubuntu3
---
gnome-settings-daemon (3.4.0-0ubuntu3) precise; urgency=low
* debian/patches/correct_logout_action.patch:
- display the logout action on ctrl-alt-del (lp: #961501)
*
** Changed in: gnome-session
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program is
For xbindkeys users, this bug is reported against Debian here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628654
The work around is to simply create a ~/.xbindkeys.noauto file (note the
leading period on the file name). This will prevent the Xsession
startup script from launching xbindkeys
** Changed in: gnome-session
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program is
launched
** Bug watch added: GNOME Bug Tracker #662528
https://bugzilla.gnome.org/show_bug.cgi?id=662528
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=662528
Importance: Unknown
Status: Unknown
** Project changed: gnome-keyring = gnome-session
** Changed
** Changed in: gnome-session
Status: Unknown = New
** Changed in: gnome-session
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two
this is a real show-stopper for gnome3; is there truly no workaround
yet?
** Also affects: gnome-session (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does anyone have a temporary work around for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program is
launched
To manage
I only have this problem on a machine upgraded to oneiric (the one still
on natty works fine), and I think my problem is that the new version of
GNOME session starts xbindkeys up before ssh-agent and gpg-agent, so
xbindkeys and processes it starts do not inherit the environment
variables. I get
I'm having a similar problem, which was very confusing until I came
across this bug report. If I launch xterm from the applications menu or
from a panel launcher created using add to panel - application
launcher - xterm, ssh-agent and gpg-agent are available.
But I normally use a custom
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-session (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
I am experiencing a variant of this, but it seems to be the same bug:
I installed terminator. when launching terminator from gnome-shell,
SSH_AUTH_SOCK has a value of the form /tmp/keyring-xx/ssh (this is normal
since I commented use-ssh-agent in /etc/X11/Xsession.options.
But when
It seems this bug is known in red hat:
https://bugzilla.redhat.com/show_bug.cgi?id=713955
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program is
launched
To manage notifications about this bug go to:
17 matches
Mail list logo
