After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 322862 - Opening sent gpg encrypted email crashes evolution
Opening sent gpg encrypted email crashes evolution
Status: RESOLVED DUPLICATE of bug 315012
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 333974 (view as bug list)
Depends on:
Reported: 2005-11-30 16:46 UTC by lee
Modified: 2013-09-13 00:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

requested stack trace (16.89 KB, text/plain)
2005-12-05 15:10 UTC, Christopher Lee

Description lee 2005-11-30 16:46:31 UTC
Distribution: Ubuntu 6.04 (dapper)
Package: Evolution
Severity: Normal
Version: GNOME2.13.2 2.5.x
Gnome-Distributor: Ubuntu
Synopsis: Opening an encrypted email in Outgoing mailbox crashes evolution
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.5.x
Description of Problem:
When opening an encrypted email in the outgoing email folder, evolution

Steps to reproduce the problem:
1. 'File->Work offline'
2. Compose and send an encrypted email (PGP encryption)
3. Double click on the message in the 'Outgoing' folder

Actual Results:

Evolution crashes.

Expected Results:

Open a window for the outgoing message, probably with an indication that
the message cannot be read by the sender (if that is the case).  It
would be nice to be able to edit the header fields at least (e.g., to
send from a different account if the current one is not able to send the
message for some reason).

How often does this happen?

Every time.

Additional Information:

I think this crash also happens the same way in previous
(non-beta/alpha) versions of Evolution.

------- Bug moved to this database by unknown@gnome.bugs 2005-11-30 16:46 UTC -------

The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was

Comment 1 Christopher Lee 2005-11-30 16:48:31 UTC
actual reporter of this bug is
Comment 2 parthasarathi susarla 2005-12-05 08:43:41 UTC
Hi Chris,
Thanks for the bug report. A stack trace of the crash would actually help in
diagnoising the problem better. And heres where you can find how to get one: 
Changing the bug to NEEDINFO, REOPEN the bug once you have the stack trace.
Comment 3 Christopher Lee 2005-12-05 15:10:32 UTC
Created attachment 55640 [details]
requested stack trace
Comment 4 Christopher Lee 2005-12-05 15:13:10 UTC
Added stack trace, but I don't seem to have permission to reset the bug status
Comment 5 parthasarathi susarla 2005-12-05 17:24:29 UTC
Copying the stack trace here for simple dup finder and re-opening bug:

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/
  • #2 libgnomeui_module_info_get
    from /usr/lib/
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 camel_mime_part_get_content_type
    from /usr/lib/
  • #6 camel_folder_change_info_free
    from /usr/lib/
  • #7 camel_cipher_decrypt
    from /usr/lib/
  • #8 e_msg_composer_add_message_attachments
    from /usr/lib/evolution/2.6/components/
  • #9 e_msg_composer_new_with_message
    from /usr/lib/evolution/2.6/components/
  • #10 em_utils_post_to_url
    from /usr/lib/evolution/2.6/components/
  • #11 em_utils_edit_message
    from /usr/lib/evolution/2.6/components/
  • #12 mail_get_messagex
    from /usr/lib/evolution/2.6/components/
  • #13 mail_cancel_all
    from /usr/lib/evolution/2.6/components/
  • #14 g_vasprintf
    from /usr/lib/
  • #15 g_main_context_dispatch
    from /usr/lib/
  • #16 g_main_context_check
    from /usr/lib/
  • #17 g_main_loop_run
    from /usr/lib/
  • #18 bonobo_main
    from /usr/lib/
  • #19 main

HMm...I seem to have seen this somewhere
Comment 6 André Klapper 2006-03-10 12:14:24 UTC
confirming as per duplicate.
setting appropriate priority/severity for crashers.
Comment 7 André Klapper 2006-03-10 12:14:57 UTC
*** Bug 333974 has been marked as a duplicate of this bug. ***
Comment 8 parthasarathi susarla 2006-11-14 20:46:01 UTC

*** This bug has been marked as a duplicate of 315012 ***