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 567726 - Crash when setting _Sending Email_ and pressing Ok in Account Editor.
Crash when setting _Sending Email_ and pressing Ok in Account Editor.
Status: RESOLVED DUPLICATE of bug 564140
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-14 10:36 UTC by thanda
Modified: 2009-01-14 14:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description thanda 2009-01-14 10:36:17 UTC
(evolution:20135): e-data-server-CRITICAL **: e_account_set_string: assertion `ea != NULL' failed

This was the following message I got when I set the _Sending Email_ 

Server Type: SMTP

Server: ***********

Server requires authentication: Checked.

Use secure connection: No encryption.

Authentication Type: Login

Pressing Ok at the end crashes evolution.
Comment 1 palfrey 2009-01-14 14:24:33 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 thanda 2009-01-14 14:37:50 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
> for more information on how to do so. Thanks in advance!
> 





(evolution:31637): e-data-server-CRITICAL **: e_account_set_string: assertion `ea != NULL' failed

Program received signal SIGSEGV, Segmentation fault.

Thread 140237169735568 (LWP 31637)

  • #0 account_changed
    at em-folder-tree-model.c line 402
  • #1 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #2 ??
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #5 imap_headers_commit
    at imap-headers.c line 131
  • #6 epl_invoke
    at e-plugin.c line 1035
  • #7 e_config_commit
    at e-config.c line 1015
  • #8 ec_dialog_response
    at e-config.c line 858
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #32 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #33 ??
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #35 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #36 main
    at main.c line 689
The program is running.  Exit anyway? (y or n) y
Comment 3 palfrey 2009-01-14 14:48:35 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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