FYI, the crash appears to happen when seahorse tries to connect to a keyserver that isn't running. And the fact that there are many dups of the bug under ubuntu and none under other distros suggests that the non- responding server is probably keyserver.ubuntu.com. So if it's easy to make that server a little more reliable, that would keep people from hitting the bug. (The bug itself should probably be fixed by GNOME 2.24.1, next month.)
-- seahorse crashed with SIGSEGV in g_value_peek_pointer() https://bugs.launchpad.net/bugs/198562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
