GNOME Bugzilla – Bug 551003
crash in Passwords and Encryption Keys: Searching a key id
Last modified: 2008-10-22 15:47:56 UTC
Version: 2.22.2 What were you doing when the application crashed? Searching a key id Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.14-108.fc9.i686 #1 SMP Mon Aug 4 14:08:11 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 79024128 vsize: 79024128 resident: 19689472 share: 12906496 rss: 19689472 rss_rlim: 4294967295 CPU usage: start_time: 1220624584 rtime: 162 utime: 131 stime: 31 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/seahorse' [Thread debugging using libthread_db enabled] [New Thread 0xb8071760 (LWP 7018)] 0x00110416 in __kernel_vsyscall ()
+ Trace 206364
Thread 1 (Thread 0xb8071760 (LWP 7018))
----------- .xsession-errors --------------------- ** (seahorse:7018): CRITICAL **: seahorse_multi_operation_take: assertion `SEAHORSE_OPERATION (op) != SEAHORSE_OPERATION (mop)' failed (seahorse:7018): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' Could not find the frame base for "IA__g_spawn_command_line_sync". Could not find the frame base for "IA__g_cclosure_marshal_VOID__VOID". Could not find the frame base for "IA__g_signal_emit". Could not find the frame base for "soup_message_finished". Could not find the frame base for "cancel_message". Could not find the frame base for "soup_session_cancel_message". Could not find the frame base for "IA__g_cclosure_marshal_VOID__INT". Could not find the frame base for "IA__g_signal_emit". Could not find the frame base for "connect_watch". Could not find the frame base for "g_io_unix_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "IA__g_spawn_sync". --------------------------------------------------
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report. *** This bug has been marked as a duplicate of 533473 ***