** Changed in: seahorse
Status: New => Fix Released
** Changed in: seahorse
Importance: Unknown => High
--
Seahorse crashes when revoking a subkey
https://bugs.launchpad.net/bugs/228876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Branch linked: lp:ubuntu/seahorse
--
Seahorse crashes when revoking a subkey
https://bugs.launchpad.net/bugs/228876
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://list
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 documentat
** Changed in: seahorse
Status: Unknown => New
--
Seahorse crashes when revoking a subkey
https://bugs.launchpad.net/bugs/228876
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
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
** Bug watch added: GNOME Bug Tracker #592956
http://bugzilla.gnome.org/show_bug.cgi?id=592956
** Changed in: se
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
** Changed in: seahorse (Ubuntu)
Importance: Undecided => Medium
** Changed in: seahorse (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
Seahorse crashes when revoking a subkey
https://bugs.launchpad.net/bugs/228876
You received this bug notification because you
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,
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 t
** Changed in: seahorse (Ubuntu)
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
Seahorse crashes when revoking a subkey
https://bugs.launchpad.net/bugs/228876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Could you try obtaining a backtrace, using the instructions described
here: https://wiki.ubuntu.com/DebuggingProgramCrash
Thank you
--
Seahorse crashes when revoking a subkey
https://bugs.launchpad.net/bugs/228876
You received this bug notification because you are a member of Ubuntu
Bugs, which
[EMAIL PROTECTED]:~$ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04
[EMAIL PROTECTED]:~$ 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 Package
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 pol
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, eve
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.
** Changed in: seahorse (Ubuntu)
Assignee: (unassigned) => Chris Couls
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 +, Chris Coulson wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. However, y
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 a
17 matches
Mail list logo
