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 364813 - crash in Encryption Keys: Sending an SSH key for L...
crash in Encryption Keys: Sending an SSH key for L...
Status: RESOLVED DUPLICATE of bug 363282
Product: seahorse
Classification: Applications
Component: general
0.9.5
Other All
: High critical
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2006-10-24 20:25 UTC by Arjan Hendriks
Modified: 2006-10-27 18:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Arjan Hendriks 2006-10-24 20:25:30 UTC
What were you doing when the application crashed?
Sending an SSH key for Login to an remote computer	


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 102305792 vsize: 0 resident: 102305792 share: 0 rss: 20004864 rss_rlim: 0
CPU usage: start_time: 1161720827 rtime: 0 utime: 2045 stime: 0 cutime:1293 cstime: 0 timeout: 752 it_real_value: 0 frequency: 70

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

(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 -1225721664 (LWP 13646)]
[New Thread -1294996576 (LWP 14323)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225721664 (LWP 13646))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-27 18:52:35 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 363282 ***