** Changed in: gnome-keyring
Importance: Unknown => Medium
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
This is fixed in jaunty now. Thanks for reporting.
** Changed in: gnome-keyring (Ubuntu)
Status: Fix Committed => Fix Released
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of Ubuntu
the issue has been fixed upstream now
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Fix Committed
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: gnome-keyring
Status: Unknown => Fix Released
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks much, Kenny. That did the trick.
I wish I knew were all this documentation existed. I'd never heard of
gconf-editor. Seems like a tool that fundamental should be right on the
ubuntu menus somewhere, but I can't find it there.
Anyway, it works. Thanks again.
--jeffp
--
Unable to dis
I have a related question. In Ubuntu 8.04, Max's workaround doesn't
work. (My initial problem was with 8.10, I know.) Max said:
1. Add the line "unset SSH_AUTH_SOCK" to ~/.xsessionrc (creating it if it
doesn't exist).
2. Run gnome-session-properties and untick "GNOME Keyring Daemon Wrapper".
Jeff,
"""
Launch gconf-editor, apps/gnome-keyring/daemon-components, uncheck ssh.
Restart X. ssh-agent should start.
"""
- http://bugzilla.gnome.org/show_bug.cgi?id=525574
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notific
On 12/03/2008 02:56 PM, Max Bowsher wrote:
> I'm using the workaround I posted on current Intrepid right now. It
> works fine at leaving you using an actual ssh-agent.
>
> As for "The daemon is still there.", well yes, nothing in the workaround
> stops it running, it just stops it preempting the ac
gnome-keyring bugs may be the root cause of the openssh bug 302252 that
I reported last week.
I clobbered several Subversion source code repositories that I access
via svn+ssh.
I can manually kill gnome-keyring-daemon to work around.
Wish ssh-agent was still the default :^(
--
Unable to disabl
Max, good question. Right now, on the computer in question, I see only
the daemon. Not the wrapper. What I saw back in mid-November (when I
first tried your workaround) I can't say. I probably had only the
daemon itself running at that time as well, but who knows.
8.10 hasn't been nearly stabl
Jeff, are you seeing gnome-keyring-daemon running (expected) or gnome-
keyring-daemon-wrapper running (not expected, and not running for me) ?
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of
I, also, am running Max's workaround. The odd thing is that even if you
do what he suggests in gnome-session-properties, you'll still see the
Gnome keyring wrapper daemon running on the machine. However, it will
stop messing with ssh keys, and the standard ssh-agent commands will
then work to let
I'm using the workaround I posted on current Intrepid right now. It
works fine at leaving you using an actual ssh-agent.
As for "The daemon is still there.", well yes, nothing in the workaround
stops it running, it just stops it preempting the actual ssh-agent.
--
Unable to disable the ssh modul
This workaround does not work with current Intrepid.
The daemon is still there.
I had to install Kenny's packages.
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Here is a workaround that can be enacted purely using non-root config:
1. Add the line "unset SSH_AUTH_SOCK" to ~/.xsessionrc (creating it if it
doesn't exist).
2. Run gnome-session-properties and untick "GNOME Keyring Daemon Wrapper".
The first makes /etc/X11/Xsession.d/90x11-common_ssh-agent n
As a workaround for myself I've built a version of the gnome-keyring
package that is compiled without ssh support and so it doesn't act as a
SSH agent...
I've attached a debdiff which will do the above, you just need to build
the package, alternatively, i've submitted the package to my PPA and you
Is there a way to simply turn off gnome-keyring-daemon? If I did that,
what else would break? I can't find it in 8.10's "services" management
UI, so I don't know if a typical user can shut it down without some sort
of nasty issues cropping up.
But, shutting it down might get me past the silly po
I can confirm this bug on a vanilla 8.10 install. I see the same error
repeated 3 times after each reboot:
Nov 5 10:45:41 dworkin gdm[4869]: gnome-keyring-daemon: couldn't lookup
keyring component setting: Failed to contact configuration server; some
possible causes are that you need to enable T
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: Confirmed => Triaged
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notificatio
** Bug watch added: GNOME Bug Tracker #558181
http://bugzilla.gnome.org/show_bug.cgi?id=558181
** Also affects: gnome-keyring via
http://bugzilla.gnome.org/show_bug.cgi?id=558181
Importance: Unknown
Status: Unknown
--
Unable to disable the ssh module of gnome-keyring
https://bugs
Further investigation reveals that between 2.22 and 2.24, gconfd grew a
dependency on dbus which clearly isn't running when gdm is invoking
PAM functions. Argh. This could be complex.
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this
Correction, I meant /var/log/auth.log not /var/log/authpriv.log above.
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Setting Status=Confirmed (two reporters, plus log message pinpointing
likely problem)
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
Unable to disable the ssh module of gnome-keyring
https://bugs.launchpad.net/bugs/275010
You received this bug notification because you a
The following message appears (repeated three times) in
/var/log/authpriv.log:
gnome-keyring-daemon: couldn't lookup keyring component setting: Failed to
contact configuration server; some possible causes are that you need to enable
TCP/IP networking for ORBit, or you have stale NFS locks due to
I confirm this regression in behaviour. It would be very nice to see
this fixed, because the ssh module of gnome-keyring has reliability
issues (sporadically failing to sign, or even killing the entire gnome-
keyring-daemon, when I run a script concurrently executing many ssh
commands).
--
Unable
25 matches
Mail list logo
