** Changed in: gnome-keyring
Status: Confirmed => Fix Released
** Changed in: gnome-keyring
Importance: Unknown => Medium
--
gnome-keyring-daemon doesn't work with simultaneous connections
https://bugs.launchpad.net/bugs/365589
You received this bug notification because you are a membe
closing the bug since that works now
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Fix Released
--
gnome-keyring-daemon doesn't work with simultaneous connections
https://bugs.launchpad.net/bugs/365589
You received this bug notification because you are a member of Ubuntu
Des
The problem was corrected in mainstream. There are still some events of
gkd failures, but I cannot make a repeatable testcase (i.e. it may
happen once a work day or may work properly for the whole week while
doing administration on the same clusters). I think the bug must be
therefore closed.
--
is anybody still having this issue in lucid?
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Incomplete
** Changed in: gnome-keyring (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
--
gnome-keyring-daemon doesn't work with simultaneous connections
http
** Changed in: gnome-keyring
Status: New => Confirmed
--
gnome-keyring-daemon doesn't work with simultaneous connections
https://bugs.launchpad.net/bugs/365589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mai
Thank you for your answer.
Then I'm stuck with maintaining my own repo for myself :-(
--
gnome-keyring-daemon doesn't work with simultaneous connections
https://bugs.launchpad.net/bugs/365589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assig
There is no real way to force volunteers to spend their free time doing
work for you no ...
--
gnome-keyring-daemon doesn't work with simultaneous connections
https://bugs.launchpad.net/bugs/365589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Sebastien, I need an advice.
The bug in GNOME hasn't even been triaged by now. I've made a patch that solves
the problem and posted
it there. Is there any way I can force developers at least to look at my patch
(and eventually the problem)?
If there is no activity on GNOME side, can we make a p
** Changed in: gnome-keyring
Status: Unknown => New
--
gnome-keyring-daemon doesn't work with simultaneous connections
https://bugs.launchpad.net/bugs/365589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs maili
Thank you for sending the bug to GNOME
** Changed in: gnome-keyring (Ubuntu)
Status: New => Triaged
** Also affects: gnome-keyring via
http://bugzilla.gnome.org/show_bug.cgi?id=580068
Importance: Unknown
Status: Unknown
--
gnome-keyring-daemon doesn't work with simultaneous
Oh, sorry.
I've filed a bug to bugzilla (http://bugzilla.gnome.org/show_bug.cgi?id=580068)
in case someone gets to launchpad with the same problems.
Thanks for redirecting.
** Bug watch added: GNOME Bug Tracker #580068
http://bugzilla.gnome.org/show_bug.cgi?id=580068
--
gnome-keyring-daemon
Thank you for your bug report, you seem to know what you are doing so
perhaps you could open your bug on bugzilla.gnome.org where the people
writting gnome-keyring will read it, that will probably work better than
relying on a bug triager not having the issue to forward comments for
you there and b
I've found a simple test case.
Assuming you have a password protected key, a local ssh server and your public
key
is in authorized_keys.
This works correctly (10 ssh sessions):
for n in `seq 10`; do ssh localhost "echo $n" & done
This fails with errors in several cases (20 ssh sessions):
for n
13 matches
Mail list logo
