** Tags removed: ubuntu-desktop-trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents gnome-keyring from being ssh agent
Status in
Here's the list of the regression bug reports caused by this update so
far:
https://bugs.launchpad.net/bugs/1387747
https://bugs.launchpad.net/bugs/1388259
https://bugs.launchpad.net/bugs/1391775
https://bugs.launchpad.net/bugs/1412624
Please comment and/or click on affects me there instead.
--
Please stop filing duplicate bugs.
The regression was fixed in vivid a long time ago and is tracked to be SRUed
again in
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I am using gnome-keyring-daemon with ssh-agent capability which broke with the
keyring-daemon 3.10.1-1ubuntu4.1.
After downgrading to gnome-keyring=3.10.1 SSH_AUTH_SOCKS is again correctly
exposed to the keyring location.
--
You received this bug notification because you are a member of
For those of us that don't want to use gnome-keyring-ssh and use ssh-
agent instead, this breaks our setup.
Previously, we were able to disable gnome-keyring-ssh by ediing
/etc/xdg/autostart/gnome-keyring-ssh.desktop and setting
NoDisplay=false. Then it would be visible in Startup Applications
I just encountered this problem and eventually found this bug.
I see exactly the behaviour described above - starting a terminal with
ctrl-alt-T gets the correct SSH_AUTH_SOCK, otherwise it's wrong.
dpkg -s gnome-keyring confirms that the fix above is
already running on my system:
% dpkg -s
I have a problem similar to the one of 'agnul' since yesterday's update
in ubuntu 14.04 (this update included gnome-keyring 3.10.1-1ubuntu4.1)
When I start a gnome-terminal with alt+F2, the environment is OK
(SSH_AUTH_SOCK set)
When I start a terminal using a keyboard shortcut, the env is OK
Additionnal note to my last comment:
After downgrading to gnome-keyring 3.10.1-1ubuntu4 (from gnome-
keyring 3.10.1-1ubuntu4.1), loging out/in, it started working again: a
terminal started form a '.desktop' file has the proper SSH_AUTH_SOCK
variable.
--
You received this bug notification
Looks like the things got worse...
Though for us at Linux Mint things haven't really changed. Running mate-
terminal via mintMenu still sets SSH_AUTH_SOCK to the wrong value (in
/tmp dir).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Based on the behavior I've observed, I think it's possible that there
are two bugs in play here, and fixing one has revealed the other one.
I'm running Xubuntu 14.04.
Before this update, starting my terminal from the applications menu
yielded a shell with SSH_AUTH_SOCK correctly pointing at
Running gnome-terminal with the Alt-F2 shortcut the SSH_AUTH_SOCKET env
variable is not set. Used to work until a couple of days ago, could this
be related?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
This bug was fixed in the package gnome-keyring - 3.10.1-1ubuntu4.1
---
gnome-keyring (3.10.1-1ubuntu4.1) trusty; urgency=medium
* debian/gnome-keyring.conf: upstart user-session job to re-export
gnome-keyring agent's sockets into the desktop environment. (LP:
#1271591)
--
Hello Marc, or anyone else affected,
Accepted gnome-keyring into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/gnome-
keyring/3.10.1-1ubuntu4.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
I upgraded gnome-keyring to 3.10.1-1ubuntu4.1 from trusty-proposed in a
virtual machine.
Before upgrading and rebooting, this bug was occurring.
After rebooting, the bug was gone. I rebooted about 5 times and tested ssh keys
using gnome-terminal (started both from the Dash and from Ctrl+Alt+T)
** Changed in: gnome-keyring (Ubuntu)
Assignee: James Hunt (jamesodhunt) = Dimitri John Ledkov (xnox)
** Changed in: gnome-keyring (Ubuntu)
Status: In Progress = Fix Released
** Changed in: gnome-keyring (Ubuntu Trusty)
Assignee: James Hunt (jamesodhunt) = Dimitri John Ledkov
@marga
with this change, gnome-keyring desktop session upstart job will take over
ssh-agent upstart job in Trusty 14.04 LTS, and thus override SSH_AUTH_SOCK with
the gnome-keyring's one. To disable this:
- system-wide: echo manual | sudo tee -a /etc/xdg/upstart/gnome-keyring.override
-
[ubuntu/trusty-proposed] gnome-keyring 3.10.1-1ubuntu4.1 (Waiting for
approval)
gnome-keyring (3.10.1-1ubuntu4.1) trusty; urgency=medium
* debian/gnome-keyring.conf: upstart user-session job to re-export
gnome-keyring agent's sockets into the desktop environment. (LP:
#1271591)
--
It seems a better way would be to fix
/etc/X11/Xsession.d/90x11-common_ssh-agent
(to start ssh-agent before gnome-keyring-daemon or not start it at all)
According to man page use of initctl set-env --global is discouraged
--
You received this bug notification because you are a member of
More than four months passed - and the fix for a bug with Importance
set to High isn't in Trusty yet?
Disappointing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
** Changed in: gnome-keyring (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) = James Hunt (jamesodhunt)
** Changed in: gnome-keyring (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Desktop
Sorry, that link is wrong. This is the correct one:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/gnome-
keyring/utopic/view/168/debian/gnome-keyring.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in
Finally found this bug report!
I have the same issue. Sometimes it happens, sometimes it doesn't.
Is the fix going to be backported to Tusty soon? That would be great.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in
In the meantime, just grab this file from here
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/gnome-keyring/utopic/view/166/debian/gnome-keyring.conf
(it's the fix) and put it in /usr/share/upstart/sessions/, then restart the
session and see if the problem is gone forever.
Still,
When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents gnome-keyring from being ssh
** Changed in: gnome-keyring (Ubuntu Trusty)
Status: In Progress = Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents
** Changed in: gnome-keyring (Ubuntu)
Status: Fix Released = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents
** Changed in: gnome-keyring (Ubuntu Trusty)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
** Changed in: gnome-keyring (Ubuntu)
Assignee: (unassigned) = Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: gnome-keyring (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents
This bug was fixed in the package gnome-keyring - 3.10.1-1ubuntu5
---
gnome-keyring (3.10.1-1ubuntu5) utopic; urgency=medium
* debian/gnome-keyring.conf: upstart user-session job to re-export
gnome-keyring agent's sockets into the desktop environment. (LP:
#1271591)
--
Is there any workaround so that all applications started from the dash
can benefit from the agent?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job
** Also affects: gnome-keyring (Ubuntu Trusty)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race
I have chosen to unlock my GPG key at login time. In processes launched
by Unity, I sometimes get the GPG_AGENT_INFO environment variable set,
but other times (in other login sessions) not. So likely some kind of
race. From terminal launched with Ctrl+Alt+T, the variable always seems
to be
** Tags added: ubuntu-desktop-trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents gnome-keyring from being ssh agent
Status in
I can confirm what Andre is saying: launching a terminal via the
launcher or the dash (or synapse) results in Unity not using gnome-
keyring. If I launch via ctrl-alt-t gnome-keyring is used.
Launch via the dash:
SSH_AGENT_PID=2253
SSH_AUTH_SOCK=/tmp/ssh-y0YsIQziIbZX/agent.2249
Launch via
I see what I think is this bug on 3 different computers running 13.10, 2
installed with 13.10, 1 upgraded from 12.10.
Often what ssh agent is tried depends on how I start the terminal - the
agent environment is set differently if started from the dash, launcher
or alt-ctrl-t. And sometimes they
gnome-keyring updates SSH_AUTH_SOCK by calling gnome-session's Setenv DBus
method.
gnome-session then calls DBus's UpdateActivationEnvironment so that dbus
activated clients also get the env variable.
Perhaps adding the upstart job, but leaving the autostart desktop files
in place is
This may also be the cause of bug 1259564
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1271591
Title:
upstart job race prevents gnome-keyring from being ssh agent
Status in
I was wondering, if that's just me or everyone. It appears that gnome-
keyring does not ship user-session jobs the default ssh-agent is used
from openssh-client package, which does ship user-session job.
So gnome-keyring should provide user session jobs for all of it's agents
export the AGENT
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop
/etc/xdg/autostart/gnome-keyring-ssh.desktop
/etc/xdg/autostart/gnome-keyring-gpg.desktop
/etc/xdg/autostart/gnome-keyring-secrets.desktop
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
39 matches
Mail list logo
