GNOME Bugzilla – Bug 550868
seahorse crashed with SIGSEGV in _seahorse_viewer_on_key_delete_gtk_action_activate()
Last modified: 2008-09-14 18:40:49 UTC
Steps to reproduce: 1. Open seahorse 2. Right-Mouse-Click a ssh-key and select delete 3. Crash Stack trace: Starting program: /usr/bin/seahorse [Thread debugging using libthread_db enabled] [New Thread 0xb7048700 (LWP 16727)] ** Message: init gpgme version 1.1.6 Program received signal SIGSEGV, Segmentation fault.
+ Trace 206330
Thread 3070527232 (LWP 16727)
Thread 1 (Thread 0xb7048700 (LWP 16727))
The program is running. Exit anyway? (y or n) Other information: The bug has also been reported on launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/264753
This should be fixed with this commit: 2008-09-07 Stef Walter <stef@memberwebs.com> * libseahorse/seahorse-key.c: Fill in abstract methods properly on the SeahorseObject class. Fixes crash.
Well, the crash does not occur anymore. But the key does not get deleted either so its still not the expected behaviour. ;-) Should I open a new bug regarding the deletion issue?
Just fixed related bug #551377 Do you think that'll do the trick?
I'll try with svn later. But looks good. Thank you.
Can confirm its fixed. Thanks again.