Bug 560188 – Crash after account change

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 560188 - Crash after account change


Summary:	Crash after account change


Status:	RESOLVED DUPLICATE of bug 552583

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.26.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	560469 562769 563483 563676 564197 564341 564470 564949 (view as bug list)
Depends on:
Blocks:

Reported:	2008-11-10 17:06 UTC by Milan Crha
Modified:	2013-09-13 01:00 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
proposed evo patch (5.95 KB, patch) 2008-11-19 15:09 UTC, Milan Crha	none	Details \| Review
proposed evo patch ][ (6.01 KB, patch) 2008-11-20 11:35 UTC, Milan Crha	none	Details \| Review

Description Milan Crha 2008-11-10 17:06:01 UTC

Evo revision: 36769
eds revision: 9743

There was a host lookup error on one account, and I changed on the same one a setting information, this was shown on the console and evo crashed immediately.
Even closing of the error message from the status bar doesn't help here.

----------------------------------------------------------------------------

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

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208813248 (LWP 25909)]
0x01329192 in account_changed (accounts=0x85b1d90, account=0x0, user_data=0x8531580) at em-folder-tree-model.c:402
402             if (!account->enabled ||!(uri = account->source->url))
(gdb) t a a bt

+ Trace 209588

Thread 1 (Thread -1208813248 (LWP 25909))

#0 account_changed
at em-folder-tree-model.c line 402
#1 IA__g_cclosure_marshal_VOID__OBJECT
at gmarshal.c line 636
#2 IA__g_closure_invoke
at gclosure.c line 767
#3 signal_emit_unlocked_R
at gsignal.c line 3244
#4 IA__g_signal_emit_valist
at gsignal.c line 2977
#5 IA__g_signal_emit
at gsignal.c line 3034
#6 e_account_list_change
at e-account-list.c line 367
#7 imap_headers_commit
at imap-headers.c line 131
#8 epl_invoke
at e-plugin.c line 1035
#9 e_plugin_invoke
at e-plugin.c line 769
#10 ech_commit
at e-config.c line 1267
#11 e_config_commit
at e-config.c line 1015
#12 ec_dialog_response
at e-config.c line 858
#13 IA__g_cclosure_marshal_VOID__INT
at gmarshal.c line 216
#14 IA__g_closure_invoke
at gclosure.c line 767
#15 signal_emit_unlocked_R
at gsignal.c line 3244
#16 IA__g_signal_emit_valist
at gsignal.c line 2977
#17 IA__g_signal_emit
at gsignal.c line 3034
#18 IA__gtk_dialog_response
at gtkdialog.c line 905
#19 action_widget_activated
at gtkdialog.c line 604
#20 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#21 IA__g_closure_invoke
at gclosure.c line 767
#22 signal_emit_unlocked_R
at gsignal.c line 3244
#23 IA__g_signal_emit_valist
at gsignal.c line 2977
#24 IA__g_signal_emit
at gsignal.c line 3034
#25 IA__gtk_button_clicked
at gtkbutton.c line 889
#26 gtk_real_button_released
at gtkbutton.c line 1484
#27 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#28 g_type_class_meta_marshal
at gclosure.c line 878
#29 IA__g_closure_invoke
at gclosure.c line 767
#30 signal_emit_unlocked_R
at gsignal.c line 3174
#31 IA__g_signal_emit_valist
at gsignal.c line 2977
#32 IA__g_signal_emit
at gsignal.c line 3034
#33 IA__gtk_button_released
at gtkbutton.c line 881
#34 gtk_button_button_release
at gtkbutton.c line 1377
#35 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#36 g_type_class_meta_marshal
at gclosure.c line 878
#37 IA__g_closure_invoke
at gclosure.c line 767
#38 signal_emit_unlocked_R
at gsignal.c line 3282
#39 IA__g_signal_emit_valist
at gsignal.c line 2987
#40 IA__g_signal_emit
at gsignal.c line 3034
#41 gtk_widget_event_internal
at gtkwidget.c line 4702
#42 IA__gtk_widget_event
at gtkwidget.c line 4499
#43 IA__gtk_propagate_event
at gtkmain.c line 2335
#44 IA__gtk_main_do_event
at gtkmain.c line 1555
#45 gdk_event_dispatch
at gdkevents-x11.c line 2365
#46 g_main_dispatch
at gmain.c line 1814
#47 IA__g_main_context_dispatch
at gmain.c line 2367
#48 g_main_context_iterate
at gmain.c line 2448
#49 IA__g_main_loop_run
at gmain.c line 2656
#50 bonobo_main
from /usr/lib/libbonobo-2.so.0
#51 main
at main.c line 694

Comment 1 Bharath Acharya 2008-11-11 06:00:45 UTC

Bumped into this one a few minutes back. Easily reproducible. Looks connected to bug #552583. The account goes NULL and hence the issues.

Comment 2 Akhil Laddha 2008-11-12 08:24:12 UTC

*** Bug 560469 has been marked as a duplicate of this bug. ***

Comment 3 Milan Crha 2008-11-19 15:09:43 UTC

Created attachment 123039 [details] [review]
proposed evo patch

for evolution;

Same function for similar things. Normalizing URLs first, to compare same things, not the different. Also comparing case insensitively, domain name is case insensitive.

Comment 4 Matthew Barnes 2008-11-19 16:02:46 UTC

CC'ing Sankar, since he had some thoughts about these functions.

Comment 5 Milan Crha 2008-11-20 11:35:55 UTC

Created attachment 123100 [details] [review]
proposed evo patch ][

for evolution;

OK, let provider compare URLs, as Sankar suggested.

Comment 6 Milan Crha 2008-11-27 22:03:36 UTC

Hmm, I saw crashing this even with the second patch, when playing with exchange account it failed to find it when looking for it in config listener in the exchange plugin. Not sure why and when, and cannot reproduce now too. I had two similar accounts, the first disabled, the second enabled, trying to setup the second one. There could be something wrong even when comparing with provider's url_equal function.

Comment 7 palfrey 2008-12-01 13:10:55 UTC

*** Bug 562769 has been marked as a duplicate of this bug. ***

Comment 8 Milan Crha 2008-12-04 11:18:09 UTC

Get rid of this in favour of bug #552583

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

Comment 9 palfrey 2008-12-08 12:59:53 UTC

*** Bug 563483 has been marked as a duplicate of this bug. ***

Comment 10 palfrey 2008-12-08 13:00:00 UTC

*** Bug 563676 has been marked as a duplicate of this bug. ***

Comment 11 Akhil Laddha 2008-12-31 04:41:05 UTC

*** Bug 564341 has been marked as a duplicate of this bug. ***

Comment 12 Akhil Laddha 2008-12-31 06:06:05 UTC

*** Bug 564470 has been marked as a duplicate of this bug. ***

Comment 13 Akhil Laddha 2008-12-31 08:46:37 UTC

*** Bug 564949 has been marked as a duplicate of this bug. ***

Comment 14 Akhil Laddha 2009-01-16 09:05:43 UTC

*** Bug 564197 has been marked as a duplicate of this bug. ***