After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 399479 - Seahorse agent crashes
Seahorse agent crashes
Status: RESOLVED INCOMPLETE
Product: seahorse
Classification: Applications
Component: general
unspecified
Other other
: High critical
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2007-01-22 18:25 UTC by brett
Modified: 2007-07-07 05:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description brett 2007-01-22 18:23:57 UTC 
Distribution: Debian 4.0
Package: seahorse
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Debian
Synopsis: Seahorse agent crashes
Bugzilla-Product: seahorse
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Crashes on addition of ssh identities

Steps to reproduce the crash:
1. Setup ssh-agent to use seahorse-agent
2. login & run ssh-add
3. 

Expected Results:


How often does this happen?
Always

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/seahorse-agent'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224751424 (LWP 16984)]
(no debugging symbols found)
0xb7f7e410 in ?? ()

+ Trace 104350

Thread 1 (Thread -1224751424 (LWP 16984))

  • #0 ??
  • #1 ??
  • #2 ??
  • #0 ?? 




------- Bug created by bug-buddy at 2007-01-22 18:25 -------
Comment 1 Adam Schreiber 2007-01-22 18:38:16 UTC 
Could you please specify  how you "1. Setup ssh-agent to use seahorse-agent"?  Also, what version of seahorse are you using?  

You shouldn't have to run ssh-add if seahorse-agent is being used properly.
Comment 2 Bruno Boaventura 2007-02-25 14:56:48 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Ted Percival 2007-07-07 05:50:07 UTC 
I filed a report with an analysis and patch for this as bug #454469.