GNOME Bugzilla – Bug 307794
Evolution crashs in Mail Account creation druid
Last modified: 2006-08-10 21:54:01 UTC
Distribution: Debian 3.1 Package: Evolution Severity: normal Version: GNOME2.11.3 unspecified Gnome-Distributor: Ubuntu Synopsis: Evolution crashs in Mail Account creation druid Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Evolution crashs suddenly when I select the server type of a new mail account. This occures even after .evolution has been deleted. Steps to reproduce the crash: 1. Start Evolution 2. Go to Edit > Preferences, then add a mail account 3. Click next, then enter name and email leaving other fields blank. 4. Click next, drop down the combo for selecting server type, then select an item. Booom. How often does this happen? This occures everytime with any item in the combo box. Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228711136 (LWP 7093)] [New Thread -1254102096 (LWP 7162)] [New Thread -1245709392 (LWP 7154)] [New Thread -1235780688 (LWP 7127)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 61050
Thread 1 (Thread -1228711136 (LWP 7093))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-15 15:45 UTC -------
Got the crash as well (with evolution/e-d-s CVS)
*** Bug 307867 has been marked as a duplicate of this bug. ***
*** Bug 308370 has been marked as a duplicate of this bug. ***
*** Bug 308505 has been marked as a duplicate of this bug. ***
Is ther any attempt to get this bug fixed? Or is it fixed in CVS? Seb
*** Bug 308911 has been marked as a duplicate of this bug. ***
*** Bug 308921 has been marked as a duplicate of this bug. ***
For what it's worth, this bug possibly occurs also on Win32. Below the output. The importer start warnings are presumably not relevant. gdb backtrace at end. (evolution-2.4.exe:10680): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_W IDGET (widget)' failed (evolution-2.4.exe:10680): GLib-GObject-CRITICAL **: g_value_get_pointer: assert ion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4.exe:10680): GLib-GObject-CRITICAL **: g_value_get_pointer: assert ion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4.exe:10680): evolution-mail-WARNING **: OAFIID:GNOME_Evolution_Mai l_Factory:2.4: Don't know what to do with OAFIID:GNOME_Evolution_Mail_Netscape_I ntelligent_Importer:2.4 ** (evolution-2.4.exe:10680): WARNING **: Could not start OAFIID:GNOME_Evolution _Mail_Netscape_Intelligent_Importer:2.4:IDL:Bonobo/GeneralError:1.0 (evolution-2.4.exe:10680): evolution-mail-WARNING **: OAFIID:GNOME_Evolution_Mai l_Factory:2.4: Don't know what to do with OAFIID:GNOME_Evolution_Mail_Pine_Intel ligent_Importer:2.4 ** (evolution-2.4.exe:10680): WARNING **: Could not start OAFIID:GNOME_Evolution _Mail_Pine_Intelligent_Importer:2.4:IDL:Bonobo/GeneralError:1.0 (evolution-2.4.exe:10680): evolution-mail-WARNING **: OAFIID:GNOME_Evolution_Mai l_Factory:2.4: Don't know what to do with OAFIID:GNOME_Evolution_Mail_Elm_Intell igent_Importer:2.4 ** (evolution-2.4.exe:10680): WARNING **: Could not start OAFIID:GNOME_Evolution _Mail_Elm_Intelligent_Importer:2.4:IDL:Bonobo/GeneralError:1.0 (evolution-2.4.exe:10680): Gtk-CRITICAL **: gtk_window_set_type_hint: assertion `!GTK_WIDGET_VISIBLE (window)' failed (evolution-2.4.exe:10680): Gtk-WARNING **: gtk_window_set_wmclass: shouldn't set wmclass after window is realized! (evolution-2.4.exe:10680): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_W IDGET (widget)' failed (evolution-2.4.exe:10680): GLib-GObject-CRITICAL **: g_value_get_pointer: assert ion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4.exe:10680): GLib-GObject-CRITICAL **: g_value_get_pointer: assert ion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4.exe:10680): GLib-GObject-CRITICAL **: g_value_get_pointer: assert ion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4.exe:10680): GLib-GObject-CRITICAL **: g_value_get_pointer: assert ion `G_VALUE_HOLDS_POINTER (value)' failed gdb: kernel event for pid=10680 tid=9704 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_ACCESS_VIOLATION at 0x0250add0 Program received signal SIGSEGV, Segmentation fault. 0x0250add0 in gtk_combo_box_menu_item_activate (item=0x4ed7900, user_data=0x4ee0fc8) at gtkcombobox.c:2769 2769 combo_box->priv->editing_canceled = FALSE; (gdb) p combo_box->priv $1 = (GtkComboBoxPrivate *) 0xfeeefeee (gdb) i thr 4 thread 10680.0x2aec 0x7c90eb94 in ntdll!LdrAccessResource () from ntdll.dll 2 thread 10680.0x24a0 0x7c90eb94 in ntdll!LdrAccessResource () from ntdll.dll * 1 thread 10680.0x25e8 0x0250add0 in gtk_combo_box_menu_item_activate ( item=0x4ed7900, user_data=0x4ee0fc8) at gtkcombobox.c:2769 (gdb) bt
+ Trace 61598
etc.
Forgot to mention, as you see the combo_box->priv is bogus. I think 0xfeefee is the filler the runtime puts in free'd memory before it gets reused, so this looks a bit like a memory corruption bug.
Presumably not related to the crash here, but the first critical assertion warning in my output above seems to be because evolution/mail/em-account-editor.c:emae_identity_page() does: gtk_widget_hide(glade_xml_get_widget(xml, "sigOption")) even if there isn't any widget called sigOption in mail-config.glade as far as I can see.
*** Bug 309617 has been marked as a duplicate of this bug. ***
*** Bug 309397 has been marked as a duplicate of this bug. ***
Created attachment 48783 [details] [review] Crude fix for this bug I have a crude fix. I have attached the patch. When you select any item from the "Server Type" combo box, it emits the "changed" signal. This invokes "emae_provider_changed" callback which in its execution path calls ec_rebuild. Here the page containing the combox box is destroyed and a new page with items specific for that selected server type is loaded. But the code in gtkcombobox.c requires that combo box for its pending opertions and is destroyed in the callback. The same happens for the combo box in the sending page also. Because the same callback is used. My fix removes that widget destruction leaving a memory leak. The combo box has to be hold and destroyed later. But how? Please review it, and give suggestions and comments.
*** Bug 309749 has been marked as a duplicate of this bug. ***
*** Bug 310211 has been marked as a duplicate of this bug. ***
*** Bug 273375 has been marked as a duplicate of this bug. ***
*** Bug 312499 has been marked as a duplicate of this bug. ***
*** Bug 312594 has been marked as a duplicate of this bug. ***
I have exactly the same problem trying to create a POP mail account. I am using Fedora 4. Here are all the evolution packages I am using: evolution-webcal-2.2.0-1 evolution-devel-2.2.2-8 evolution-2.2.2-8 evolution-data-server-1.2.2-3 evolution-data-server-devel-1.2.2-3 evolution-connector-2.2.2-5 My crash report is very similar to the one above.
*** Bug 313032 has been marked as a duplicate of this bug. ***
*** Bug 313342 has been marked as a duplicate of this bug. ***
*** Bug 314388 has been marked as a duplicate of this bug. ***
still happening using evolution-2.4.0.0.200508300318-0.snap.novell.11.1 After an account is created goto the account editor in edit > preferences. Select the account and click on edit. Now from the receiving email tab, keep switching between different server types. After the server type has been changed for about 3 times, evolution crashes. Here is the stack trace:
+ Trace 62688
Thread 1 (Thread 1097744000 (LWP 8644))
*** Bug 311554 has been marked as a duplicate of this bug. ***
reproducible when switching it again and again (fast):
+ Trace 63279
*** Bug 307834 has been marked as a duplicate of this bug. ***
This bug does not occur for me anymore in Evo 2.6 Is it OK to close this bug?
Jaap A: If u were observing this bug earlier and not observing now you can close it.
*** Bug 326556 has been marked as a duplicate of this bug. ***
(In reply to comment #28) > Jaap A: If u were observing this bug earlier and not observing now you can > close it. I do count no less than 20 duplicates / confirmations. IMHO this bug can *not* be closed, unless a developer assures that this has been fixed, the code in question being obsoleted, or at a very minimum a stronger evidence of this to not be an issue any longer. Did anyone have a close look at this crash at all? *ping* All those CRITICAL warnings in comment 8 are quite scary anyway...
Crasher, lots of dupes. Priority High, Severity Critical.
a patch creating a memory leak is not the way to, i guess. if anyone can still reproduce this in 2.6, please raise your hand. thanks.
Retested on 2.7.91. It is fixed.