Seahorse crashes when revoking a subkey

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. (Change enabled to '1' and then do sudo /etc/init.d/apport restart). Once you have enabled Apprt, try to repeat the crash.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Apport was enabled. The reason I did not submit this bug with Apport was
because it wasn't triggered by this crash. /var/crash was also empty.
On Sat, 2008-05-10 at 11:28 +0000, Chris Coulson wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. However, your crash report is either missing or
> challenging to deal with. Please follow these instructions to have
> apport report a new bug about your crash that can be dealt with by the
> automatic retracer.
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart. (Change enabled to '1' and
> then do sudo /etc/init.d/apport restart). Once you have enabled Apprt,
> try to repeat the crash.
>
> If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
> If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
>
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.
>
> ** Changed in: seahorse (Ubuntu)
> Status: New => Invalid
>

Could you try running seahorse from the terminal and post the output when you repeat the crash? In another terminal, could you run 'tail -f /var/log/messages' and monitor what goes here whilst you repeat the crash as well.

This gets sent to stderr:
** Message: init gpgme version 1.1.5

(seahorse:7423): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
seahorse: rungpg.c:608: command_handler: Assertion `gpg->cmd.code' failed.

This gets printed to the terminal, even though I redirected both stdout and stderr:
Aborted (core dumped)

Ok, just tried doing a kill -6 `pidof seahorse` on my machine, and Apport doesn't generate a crash report for SIGABRT, so I'll re-open the bug.

I can't get Seahorse to crash though. Could you give some more information by typing the following in to a terminal please:
lsb_release -rd
apt-cache policy seahorse

Thanks

caleb@caleb-laptop:~$ lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04
caleb@caleb-laptop:~$ apt-cache policy seahorse
seahorse:
  Installed: 2.22.1-0ubuntu2
  Candidate: 2.22.1-0ubuntu2
  Version table:
 *** 2.22.1-0ubuntu2 0
        500 http://ubuntu.media.mit.edu hardy/main Packages
        100 /var/lib/dpkg/status

Could you try obtaining a backtrace, using the instructions described here: https://wiki.ubuntu.com/DebuggingProgramCrash

Thank you

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Attached is the full backtrace.

To trigger the crash, I started seahorse, selected my key, clicked "properties", clicked "details", selected my DSA primary key, and clicked "Revoke". I selected "Superseded" from the drop-down menu and put "Key superseded by RSA/RSA key 40E0D7C2 generated May 24th, 2009" into the Description field, then clicked Revoke. At that point, seahorse aborts.

More information to go along with Ted's gdb backtrace.

1] Revoke, Superseded - blank comment field. Seahorse gives dialog:
Couldn't revoke subkey
General error

And .xsession-errors shows:
** (seahorse:6771): CRITICAL **: file seahorse-gpgme-key-op.c: line 1759 (rev_subkey_transit): should not be reached

2] Revoke, Superseded - anything entered in comment field. Seahorse exits and .xsession-errors shows:
seahorse: rungpg.c:652: command_handler: Assertion `gpg->cmd.code' failed.

How can I start talk about finding a replacement for seahorse in Ubuntu - I've had nothing but trouble since 8.04. It can't sync properly, it lets you sign your own key but wont let you see/remove the sig, and now it can't revoke. Useless.

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: http://bugzilla.gnome.org/show_bug.cgi?id=592956

This bug was fixed in the package seahorse - 2.29.91-0ubuntu1

---------------
seahorse (2.29.91-0ubuntu1) lucid; urgency=low

  * New upstream version:
    - Change default key lengths for subkey generation.
    - Remove unused variables
    - Revoking subkey now works again. Also minor documentation changes.
      (lp: #228876)
    - Don't show the passphrase in plaintext.
    - Check the OpenPGP engine only
    - Fixed wrong variable names in comments
    - Clean up version constants
    - Fixed two warnings at compile time
    - Unescape URI's before presenting them to the user.
    - Updated year in the copyright string of the about dialog
    - Fixed incorrect signal name
    - Fixed bug in the public key properties GUI.
  * debian/patches/90_autoconf.patch:
    - updated to the new version
 -- Sebastien Bacher <email address hidden> Mon, 22 Feb 2010 10:46:38 +0100