GNOME Bugzilla – Bug 573602
crash in Passwords and Encryption Keys: I tried to add a key ser...
Last modified: 2009-03-02 02:46:30 UTC
Version: 2.24.1 What were you doing when the application crashed? I tried to add a key server. In the "Add Key Server" dialog I selected "Custom", and the program crashed immediately after. Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 50233344 vsize: 50233344 resident: 19968000 share: 12136448 rss: 19968000 rss_rlim: 18446744073709551615 CPU usage: start_time: 1235887265 rtime: 59 utime: 53 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/seahorse' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb7f48a00 (LWP 31760)] 0x00643416 in __kernel_vsyscall ()
+ Trace 213007
Thread 1 (Thread 0xb7f48a00 (LWP 31760))
----------- .xsession-errors (95 sec old) --------------------- ** (seahorse:22643): CRITICAL **: gconf_notification: assertion `SEAHORSE_IS_KEY_MANAGER_STORE (skstore)' failed ** (seahorse:22643): CRITICAL **: seahorse_widget_get_toplevel: assertion `widget != NULL' failed (seahorse:22643): Gtk-CRITICAL **: gtk_window_get_size: assertion `GTK_IS_WINDOW (window)' failed ** (seahorse:22643): CRITICAL **: seahorse_widget_get_toplevel: assertion `widget != NULL' failed (seahorse:22643): Gtk-CRITICAL **: gtk_window_get_size: assertion `GTK_IS_WINDOW (window)' failed ** Message: init gpgme version 1.1.7 ** Message: init gpgme version 1.1.7 ** Message: init gpgme version 1.1.7 --------------------------------------------------
Same for Seahorse 2.25.91, see backtrace: (gdb) backtrace full
+ Trace 213043
Created attachment 129821 [details] backtrace
Created attachment 129822 [details] thread stacktrace
Thanks for catching it and researching it thoroughly. I've committed a fix which will be included in 2.25.92 and later releases.