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 336733 - Crash when SMIME encrypted message is selected on start of evolution
Crash when SMIME encrypted message is selected on start of evolution
Status: RESOLVED DUPLICATE of bug 334848
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-03-31 13:42 UTC by Jon Schewe
Modified: 2006-03-31 17:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Jon Schewe 2006-03-31 13:42:11 UTC 
Distribution: Unknown
Package: Evolution
Severity: critical
Version: GNOME2.12.0 2.4.x
Gnome-Distributor: SUSE
Synopsis: Crash when SMIME encrypted message is selected on start of evolution
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.4.x
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Crash on startup when an SMIME encrypted message is selected in an IMAP
folder.  I suspect this is a race condition of sorts.

Steps to reproduce the crash:
1. Select an SMIME encrypted message
2. Close evolution
3. Open Evolution
4. type in passwords for IMAP and Exchange accounts
5. watch evolution crash

It also crashes if I type in the SMIME password and skip the others. 
Once either set of passwords is done eveolution will crash.

Expected Results:
Evolution starting up

How often does this happen?
Always.

Additional Information:
The only workaround appears to be able to select a different message
that it's encrypted before typing in any passwords.


Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1097051872 (LWP 12495)]
[New Thread 1224764336 (LWP 12536)]
[Thread debugging using libthread_db enabled]
[New Thread 1097051872 (LWP 12495)]
[New Thread 1224764336 (LWP 12536)]
[Thread debugging using libthread_db enabled]
[New Thread 1097051872 (LWP 12495)]
[New Thread 1224764336 (LWP 12536)]
[New Thread 1222663088 (LWP 12535)]
[New Thread 1163148208 (LWP 12527)]
[New Thread 1220561840 (LWP 12526)]
[New Thread 1218460592 (LWP 12525)]
[New Thread 1216359344 (LWP 12511)]
[New Thread 1214258096 (LWP 12510)]
[New Thread 1167068080 (LWP 12507)]
[New Thread 1162881968 (LWP 12505)]
[New Thread 1160780720 (LWP 12504)]
[New Thread 1158679472 (LWP 12503)]
[New Thread 1152711600 (LWP 12501)]
[New Thread 1150487472 (LWP 12500)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 67366

Thread 1 (Thread 1097051872 (LWP 12495))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 strcmp
    from /lib/tls/libc.so.6
  • #6 e_passwords_ask_password
    from /opt/gnome/lib/libedataserverui-1.2.so.6
  • #7 g_cclosure_marshal_VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #9 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #12 gtk_dialog_response
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #13 gtk_dialog_response
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #19 gtk_button_clicked
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #20 gtk_button_get_alignment
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #21 gtk_button_get_alignment
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #22 gtk_marshal_VOID__UINT_STRING
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #23 g_cclosure_new_swap
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #25 g_signal_stop_emission
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #28 gtk_widget_activate
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #29 gtk_propagate_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #30 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #31 gdk_screen_get_setting
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #32 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #33 g_main_context_check
    from /opt/gnome/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #35 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #36 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-03-31 13:42 -------
Comment 1 Karsten Bräckelmann 2006-03-31 17:57:31 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


Stacktrace matches the one in bug 334848 and its duplicate.

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