GNOME Bugzilla – Bug 605617
crash in Passwords and Encryption Keys: I was just starting sea...
Last modified: 2018-08-03 19:16:33 UTC
Version: 2.29.4 What were you doing when the application crashed? I was just starting seahorse. The UI hadn't mapped yet. I've had trouble with gnome-keyring since updating/reverting from/back to 2.28.2 to 2.29.4. See https://bugzilla.gnome.org/show_bug.cgi?id=605512 Distribution: Slackware Slackware 12.2.0 Gnome Release: 2.29.4 2009-12-24 (GARNOME) BugBuddy Version: 2.28.0 System: Linux 2.6.32.2 #53 SMP PREEMPT Thu Dec 24 21:07:01 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10799003 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad Memory status: size: 44924928 vsize: 44924928 resident: 14934016 share: 11796480 rss: 14934016 rss_rlim: 18446744073709551615 CPU usage: start_time: 1262021686 rtime: 42 utime: 37 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/garnome-svn-2.29/bin/seahorse' [Thread debugging using libthread_db enabled] [New Thread 0xb62196d0 (LWP 3824)] 0xb6bf614e in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 219808
Thread 1 (Thread 0xb62196d0 (LWP 3824))
*** Bug 606242 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/40.