[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2014-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package openssh - 1:6.6p1-1 --- openssh (1:6.6p1-1) unstable; urgency=medium [ Colin Watson ] * Apply various warning-suppression and regression-test fixes to gssapi.patch from Damien Miller. * New upstream release

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2014-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package openssh - 1:6.6p1-1 --- openssh (1:6.6p1-1) unstable; urgency=medium [ Colin Watson ] * Apply various warning-suppression and regression-test fixes to gssapi.patch from Damien Miller. * New upstream release

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2014-03-26 Thread Bruno Vasselle
Down again after last upgrade. Here's my ssh-agent.conf ** Attachment added: ssh-agent.conf https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1244736/+attachment/4045297/+files/ssh-agent.conf -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2014-03-26 Thread Bruno Vasselle
Down again after last upgrade. Here's my ssh-agent.conf ** Attachment added: ssh-agent.conf https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1244736/+attachment/4045297/+files/ssh-agent.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-12-04 Thread Guillaume Martres
** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu.

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-12-04 Thread Launchpad Bug Tracker
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/1244736

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-12-04 Thread Guillaume Martres
** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Changed in: openssh (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/1244736

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-12-04 Thread Guillaume Martres
Using: grep -q ^use-ssh-agent$ /etc/X11/Xsession.options || { stop; exit 0; } To detect whether or not to launch the ssh agent doesn't seem to make sense to me, since if use-ssh-agent is true then ssh-agent will be setup by /etc/X11/Xsession.d/90x11-common_ssh-agent (and later launched), so

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-10-26 Thread Bruno Vasselle
I've also added two lines to protect the killing part, which I did not mention above. Don't know whether it's useful or not. By the end of pre-start: initctl set-env --global SSH_AGENT_LAUNCHER=/usr/share/upstart/sessions/ssh-agent.conf By the beginning of post-stop: [

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-10-25 Thread Bruno Vasselle
This does not affect gnome-session, but openssh-client... I'm pretty sure I've said so before posting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244736 Title: upstart configuration for user

[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

2013-10-25 Thread Bruno Vasselle
Also, this does not seem to be related to Bug #959506, as this one is pretty old, and my config used to work before 13.10. It seems however to relate somehow loosely to Bug #1181510. I'm adding a comment in both Bugs -- You received this bug notification because you are a member of Ubuntu Bugs,