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 408005 - crash in Encryption Keys: Creating a remote SSH ke...
crash in Encryption Keys: Creating a remote SSH ke...
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: 2007-02-14 21:10 UTC by Rob Sharp
Modified: 2007-02-18 00:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Rob Sharp 2007-02-14 21:10:24 UTC 
What were you doing when the application crashed?
Creating a remote SSH key, having just entered my remote login username and hostname.


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

Memory status: size: 42086400 vsize: 0 resident: 42086400 share: 0 rss: 15183872 rss_rlim: 0
CPU usage: start_time: 1171487349 rtime: 0 utime: 1015 stime: 0 cutime:503 cstime: 0 timeout: 512 it_real_value: 0 frequency: 153

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 -1226504000 (LWP 8462)]
[New Thread -1238631520 (LWP 8486)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 110784

Thread 1 (Thread -1226504000 (LWP 8462))

  • #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 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-02-18 00:20:29 UTC
        



Thanks for taking the time to report this bug
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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