Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=454186.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
** Changed in: gnome-keyring
Importance: Unknown => Critical
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs
** Changed in: gnome-keyring (Fedora)
Status: Confirmed => Fix Released
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
the new version is in jaunty now
** Changed in: gnome-keyring (Ubuntu)
Assignee: hyperair (hyperair) => (unassigned)
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
the new version is in jaunty now
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Fix Released
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
On Sun, 2009-02-01 at 19:09 +, Felipe Figueiredo wrote:
> On Sun, Feb 1, 2009 at 3:51 PM, hyperair wrote:
> > On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote:
> >> Thanks for your work here. The thing is that there is already a new
> >> gnome-keyring version available (2.2
On Sun, Feb 1, 2009 at 3:51 PM, hyperair wrote:
> On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote:
>> Thanks for your work here. The thing is that there is already a new
>> gnome-keyring version available (2.25.5.) which FTBFS for the moment on
>> jaunty. I am currently workin
On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote:
> Thanks for your work here. The thing is that there is already a new
> gnome-keyring version available (2.25.5.) which FTBFS for the moment on
> jaunty. I am currently working with upstream to fix that. I'll integrate
> your wor
Thanks for your work here. The thing is that there is already a new
gnome-keyring version available (2.25.5.) which FTBFS for the moment on
jaunty. I am currently working with upstream to fix that. I'll integrate
your work in the next package for jaunty (this week I think).
--
no ssh-agent after
** Changed in: gnome-keyring (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => hyperair (hyperair)
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
And here's a debdiff for Jaunty's gnome-keyring.
--
Chow Loong Jin
** Attachment added: "gnome-keyring_2.25.4.1-0ubuntu1_2.25.4.1-0ubuntu2.debdiff"
http://launchpadlibrarian.net/21874098/gnome-keyring_2.25.4.1-0ubuntu1_2.25.4.1-0ubuntu2.debdiff
--
no ssh-agent after resume from hibernate
** Description changed:
- Binary package hint: seahorse
+ Binary package hint: gnome-keyring
- After resume from hibernate (and not suspend) seahorse-daemon and
- seahorse-agent processes are not running, and there is no other ssh-
- agent available making it annoying to use ssh, and impossible
..looks like I messed up the previous patch as well. Here's one that's
tested (I finally had the sense to test it before uploading).
--
Chow Loong Jin
** Attachment removed: "intrepid-debdiff"
http://launchpadlibrarian.net/21858990/intrepid-debdiff
** Attachment removed: "intrepid-debdiff"
Okay, it seems that the previous debdiff had a typo in it so it FTBFS'd.
Attached is one which shouldn't FTBFS.
--
Chow Loong Jin
** Attachment added: "intrepid-debdiff"
http://launchpadlibrarian.net/21865694/intrepid-debdiff
--
no ssh-agent after resume from hibernate
https://bugs.launchpa
On Sat, 2009-01-31 at 18:46 +, Felipe Figueiredo wrote:
> On Sat, Jan 31, 2009 at 6:07 AM, hyperair wrote:
> > On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote:
> >> ** Changed in: gnome-keyring
> >>Status: New => Fix Released
> >>
> > Well, it seems upstream fixed the issue
On Sat, Jan 31, 2009 at 6:07 AM, hyperair wrote:
> On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote:
>> ** Changed in: gnome-keyring
>>Status: New => Fix Released
>>
> Well, it seems upstream fixed the issue in trunk. So we just have to
> wait for the next release of gnome-keyrin
On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote:
> ** Changed in: gnome-keyring
>Status: New => Fix Released
>
Well, it seems upstream fixed the issue in trunk. So we just have to
wait for the next release of gnome-keyring, and it should be fixed
there.
--
Chow Loong Jin
--
** Changed in: gnome-keyring
Status: New => Fix Released
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bu
** Changed in: gnome-keyring (Fedora)
Status: Unknown => Confirmed
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I can confirm that hyperair's workaround works, and it's better, since
it requires no user intervention, and it's easier for newbies.
I still believe that this is a bug, not a feature, since there appears
to be no obvious way to restart the g-k-m after a hibernation/suspend,
if the mentioned optio
** Also affects: gnome-keyring (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=454186
Importance: Unknown
Status: Unknown
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Alright, I can confirm that adjusting the gnome_keyring_hibernate
setting to false (unchecked) seems to solve the said issue. My gnome
keyring doesn't crash any more upon hibernation.
--
Chow Loong Jin
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You receive
** Changed in: gnome-keyring
Status: Unknown => New
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@li
On Mon, 2009-01-26 at 22:01 +, Sean Hodges wrote:
> Work-around works great for me, thanks Felipe.
>
> Possibly related bug: https://bugs.launchpad.net/ubuntu/+source/gnome-
> keyring/+bug/220165. Suggests adjusting the gnome_keyring_hibernate
> setting in gconf-editor.
>
> Related bug at Red
** Changed in: gnome-keyring (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: Confirmed => Triaged
** Also affects: gnome-keyring via
http://bugzilla.gnome.org/show_bug.cgi?id=569253
Importance: Unknown
Status: Unknown
** Changed in: gnome-key
I reproduced this issue on Intrepid by starting gnome-keyring-daemon in
the foreground and then sending the computer into hibernate:
tstarl...@shimmer:~$ killall gnome-keyring-daemon
tstarl...@shimmer:~$ gnome-keyring-daemon -f
** Message: another SSH agent is running at: /tmp/keyring-3pQJ5l/ssh
G
Work-around works great for me, thanks Felipe.
Possibly related bug: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/220165. Suggests adjusting the gnome_keyring_hibernate
setting in gconf-editor.
Related bug at Redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=454186
Upstream bu
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop
There's no command line option to pass a directory to g-k-d in runtime.
I'll open a wishlist bug to be triaged for this.
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I found that to use a workaround to restart gnome-keyring-daemon from
command line in a way to reuse the existing socket: the env var
GNOME_KEYRING_TEST_PATH. This var should be set to the /tmp/keyring-
that was previously in use.
For example:
GNOME_KEYRING_TEST_PATH=/tmp/keyring-pw7JIX/
I originally reported this bug against seahorse, since it appears as
argument to ssh-agent in the processes list.
I'd like to correct the testcase. Although it happened that seahorse
died when I decided to post the bug, I cannot reproduce it, therefore
I'm forced to attribute this event to chance.
Reassigning to seahorse-plugins, this is the package where seahorse-
agent is in intrepid.
** Changed in: seahorse-plugins (Ubuntu)
Sourcepackagename: seahorse => seahorse-plugins
Importance: Undecided => Medium
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/26814
Related bugs (not dups): bug #99065 and #70752
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs mailing list
desktop-b
33 matches
Mail list logo
