GNOME Bugzilla – Bug 691966
[abrt] Crash in imapx_untagged_fetch()
Last modified: 2015-08-07 06:56:09 UTC
Created attachment 233682 [details] full gdb log Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffaf7fe700 (LWP 16878)] imapx_untagged_fetch (is=0x7fffa8006e20, stream=<optimized out>, cancellable=<optimized out>, error=<optimized out>) at camel-imapx-server.c:1769 1769 r = &g_array_index (data->infos, struct _refresh_info, mid);
Yet another downstream bug report from 3.6.2-3: https://bugzilla.redhat.com/show_bug.cgi?id=901798
+ Trace 231406
Thread 1 (Thread 0x7fe610805700 (LWP 15045))
This is happening to me *every* day with Evolution 3.6 (Fedora 18), to the point that I am considering uninstalling it and switching to a different application.
+ Trace 231633
This should help stop the bleeding until we can properly investigate why that assertion is being hit in the first place. https://git.gnome.org/browse/evolution-data-server/commit/?id=5c498a63bed8b6253c00f3d7edeab7077ad31e33
In case it helps it appears to me that every other day evo starts fetching all over again all email in my inbox folder. This is pretty often when this assertion is hit. No idea why evolution needs to fetch all my email all over again almost every day, but I guess that's another bug.
It might be related to bug #693101. I do not know what exact version of evolution you use, but try to update for 3.6.4, please. Also, could you run evolution with imapx debugging on, thus it'll show what was received and hopefully help to find why it crashed? You can do that when you run evolution in a terminal like this: $ CAMEL_DEBUG=imapx evolution It logs basically everything between evolution and your IMAP server. The interesting part will be shown above the crash - I do not know how many lines, though. I would also try to turn off QResync in account Properties, in case you use it.
+1 me too. Fedora 18, latest evolution. Abrt sent me here: https://bugzilla.redhat.com/show_bug.cgi?id=901798
Maybe the following trace from my gdb session is related to this, and will help to solve this problem. I experience this type of problem regularly. Let me know if you need more information: [Thread 0x7fff46e97700 (LWP 16357) exited] [Thread 0x7fff48e9b700 (LWP 16344) exited] [New Thread 0x7fff48e9b700 (LWP 16358)] [New Thread 0x7fff46e97700 (LWP 16359)] [New Thread 0x7fffcb129700 (LWP 16360)] [New Thread 0x7fff47e99700 (LWP 16361)] [Thread 0x7fffca928700 (LWP 16345) exited] [Thread 0x7fffcb129700 (LWP 16360) exited] [Thread 0x7fff47e99700 (LWP 16361) exited] ** camel:ERROR:camel-imapx-server.c:1782:imapx_untagged_fetch: code should not be reached Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fff47698700 (LWP 16354)] 0x0000003da9035ba5 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install GConf2-3.2.5-3.fc18.x86_64 PackageKit-gtk3-module-0.8.7-1.fc18.x86_64 adwaita-gtk3-theme-3.6.5-1.fc18.x86_64 at-spi2-atk-2.6.2-1.fc18.x86_64 at-spi2-core-2.6.3-1.fc18.x86_64 atk-2.6.0-1.fc18.x86_64 cairo-1.12.14-1.fc18.x86_64 cairo-gobject-1.12.14-1.fc18.x86_64 cyrus-sasl-lib-2.1.23-37.fc18.x86_64 dbus-glib-0.100-1.fc18.x86_64 dbus-libs-1.6.8-2.fc18.x86_64 dconf-0.14.1-3.fc18.x86_64 enchant-1.6.0-5.fc18.x86_64 evolution-ews-3.6.4-1.fc18.x86_64 expat-2.1.0-4.fc18.x86_64 fontconfig-2.10.2-2.fc18.x86_64 freetype-2.4.10-4.fc18.x86_64 gamin-0.1.10-13.fc18.x86_64 gcr-3.6.2-3.fc18.x86_64 gdk-pixbuf2-2.26.5-1.fc18.x86_64 geoclue-0.12.99-1.fc18.x86_64 glib-networking-2.34.2-1.fc18.x86_64 glibc-2.16-30.fc18.x86_64 gnome-desktop3-3.6.3-1.fc18.x86_64 gnome-online-accounts-3.6.3-1.fc18.x86_64 gnome-shell-3.6.3.1-1.fc18.x86_64 google-talkplugin-3.17.0.0-1.x86_64 graphite2-1.1.1-4.fc18.x86_64 gstreamer1-1.0.6-1.fc18.x86_64 gstreamer1-plugins-base-1.0.6-1.fc18.x86_64 gtk2-2.24.16-1.fc18.x86_64 gtkhtml3-4.6.4-1.fc18.x86_64 gvfs-1.14.2-3.fc18.x86_64 harfbuzz-0.9.12-2.fc18.x86_64 hunspell-1.3.2-10.fc18.x86_64 ibus-gtk3-1.5.1-2.fc18.x86_64 ibus-libs-1.5.1-2.fc18.x86_64 json-glib-0.15.2-1.fc18.x86_64 keyutils-libs-1.5.5-3.fc18.x86_64 krb5-libs-1.10.3-14.fc18.x86_64 libICE-1.0.8-2.fc18.x86_64 libSM-1.2.1-2.fc18.x86_64 libX11-1.5.0-3.fc18.x86_64 libXau-1.0.6-4.fc18.x86_64 libXcomposite-0.4.3-4.fc18.x86_64 libXcursor-1.1.13-2.fc18.x86_64 libXdamage-1.1.3-4.fc18.x86_64 libXext-1.3.1-2.fc18.x86_64 libXfixes-5.0-3.fc18.x86_64 libXi-1.6.2-1.fc18.x86_64 libXinerama-1.1.2-2.fc18.x86_64 libXrandr-1.4.0-1.fc18.x86_64 libXrender-0.9.7-2.fc18.x86_64 libXt-1.1.3-1.fc18.x86_64 libXxf86vm-1.1.2-2.fc18.x86_64 libbluray-0.2.3-1.fc18.x86_64 libcanberra-0.30-2.fc18.x86_64 libcanberra-gtk3-0.30-2.fc18.x86_64 libcom_err-1.42.5-1.fc18.x86_64 libcroco-0.6.8-1.fc18.x86_64 libcurl-7.27.0-7.fc18.x86_64 libdb-5.3.21-3.fc18.x86_64 libdrm-2.4.42-1.fc18.x86_64 libffi-3.0.10-3.fc18.x86_64 libgcc-4.7.2-8.fc18.x86_64 libgcrypt-1.5.0-8.fc18.x86_64 libgdata-0.13.1-2.fc18.x86_64 libgnome-keyring-3.6.0-1.fc18.x86_64 libgpg-error-1.10-3.fc18.x86_64 libgweather-3.6.2-1.fc18.x86_64 libical-0.48-3.fc18.x86_64 libicu-49.1.1-8.fc18.x86_64 libidn-1.26-1.fc18.x86_64 libjpeg-turbo-1.2.90-1.fc18.x86_64 libmodman-2.0.1-5.fc18.x86_64 libnotify-0.7.5-3.fc18.x86_64 liboauth-0.9.7-1.fc18.x86_64 libogg-1.3.0-2.fc18.x86_64 libpng-1.5.13-1.fc18.x86_64 libproxy-0.4.11-1.fc18.x86_64 libquvi-0.4.1-2.fc18.x86_64 librsvg2-2.36.4-1.fc18.x86_64 libselinux-2.1.12-7.3.fc18.x86_64 libsoup-2.40.3-1.fc18.x86_64 libssh2-1.4.3-1.fc18.x86_64 libstdc++-4.7.2-8.fc18.x86_64 libtdb-1.2.11-1.fc18.x86_64 libtool-ltdl-2.4.2-7.fc18.x86_64 libuuid-2.22.2-6.fc18.x86_64 libvorbis-1.3.3-3.fc18.x86_64 libwayland-client-1.0.5-1.fc18.x86_64 libwayland-server-1.0.5-1.fc18.x86_64 libxcb-1.9-1.fc18.x86_64 libxkbfile-1.0.8-2.fc18.x86_64 libxml2-2.9.0-3.fc18.x86_64 libxslt-1.1.27-2.fc18.x86_64 libytnef-1.5-9.fc18.x86_64 lua-5.1.4-11.fc18.x86_64 mesa-libEGL-9.1-3.fc18.x86_64 mesa-libGL-9.1-3.fc18.x86_64 mesa-libgbm-9.1-3.fc18.x86_64 mesa-libglapi-9.1-3.fc18.x86_64 nspr-4.9.5-2.fc18.x86_64 nss-3.14.3-1.fc18.x86_64 nss-softokn-3.14.3-1.fc18.x86_64 nss-softokn-freebl-3.14.3-1.fc18.x86_64 nss-sysinit-3.14.3-1.fc18.x86_64 nss-util-3.14.3-1.fc18.x86_64 openldap-2.4.34-1.fc18.x86_64 openssl-libs-1.0.1e-4.fc18.x86_64 orc-0.4.17-2.fc18.x86_64 p11-kit-0.14-1.fc18.x86_64 pango-1.32.3-1.fc18.x86_64 pcre-8.31-4.fc18.x86_64 pixman-0.28.0-1.fc18.x86_64 rhythmbox-2.98-4.fc18.x86_64 sqlite-3.7.13-2.fc18.x86_64 systemd-libs-197-1.fc18.2.x86_64 totem-mozplugin-3.6.3-2.fc18.x86_64 totem-pl-parser-3.4.3-1.fc18.x86_64 webkitgtk3-1.10.2-3.fc18.x86_64 xz-libs-5.1.2-2alpha.fc18.x86_64 zlib-1.2.7-9.fc18.x86_64 (gdb) quit A debugging session is active. Inferior 1 [process 29439] will be killed. Quit anyway? (y or n) n Not confirmed. (gdb) thread apply all bt
+ Trace 231817
(gdb) quit A debugging session is active. Inferior 1 [process 29439] will be killed. Quit anyway? (y or n) y
(In reply to comment #7) BTW: $ evolution --version evolution 3.6.4
same here on a F18
There had been just filled a duplicate of this in 3.10.4 downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1073281 Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: evolution --component=mail crash_function: imapx_untagged_fetch executable: /usr/bin/evolution kernel: 3.13.5-200.fc20.x86_64 Core was generated by `evolution --component=mail'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 233275
Thread 8 (Thread 0x7fe364ac2a40 (LWP 3569))
Another bug, this time from 3.12.8: https://bugzilla.redhat.com/show_bug.cgi?id=1168832 Evo crashed after resuming from suspend. I'm using evolution 3.12.8-1.fc21 and evolution-data-server 3.12.8-2.fc21.
+ Trace 234377
Thread 1 (Thread 0x7f5bba7fc700 (LWP 14228))
Created attachment 292190 [details] Valgrind log I've apparently been able to reproduce the problem while running Evo under Valgrind, but I can't see the error that made Evo to stop. In bash, "Processus arrêté" ("Process stopped", not sure what this means) was printed, and when starting Evo it proposed my to recover the message I was trying to send, so it looks like the crash happened. But Valgrind makes it look like Evo ended normally, or I must be missing the interesting message in the noise.
Thanks for the update. The valgrind log shows something usable, namely: > evolution-shell-Message: Network disconnected. Forced offline. > evolution-shell-Message: Connection established. Going online. > > (evolution:9269): camel-imapx-WARNING **: (camel-imapx-server.c:7677): > imapx_ready_to_read: runtime check failed: (local_error != NULL) There there are some memory issues reported, which finally results in a process termination. The first invalid memory read related to IMAPx (or better discovered when running IMAPx code) is shown below. I suppose there happened a memory corruption, maybe a double-free, maybe related to the 'local_error != NULL' error above. > Thread 17 pool: > Invalid read of size 8 > at 0x3F1E864FE3: g_network_address_address_enumerator_next (gnetworkaddress.c:903) > by 0x3F1E86DFA5: g_proxy_address_enumerator_next (gproxyaddressenumerator.c:210) > by 0x3F1E87A212: g_socket_client_connect (gsocketclient.c:1011) > by 0x312488161F: network_service_connect_sync (camel-network-service.c:650) > by 0xFA2434F: imapx_connect_to_server (camel-imapx-server.c:4520) > by 0xFA2602C: imapx_reconnect (camel-imapx-server.c:4906) > by 0xFA2602C: camel_imapx_server_connect (camel-imapx-server.c:8268) > by 0xFA0C55B: imapx_create_new_connection_unlocked (camel-imapx-conn-manager.c:793) > by 0xFA0C55B: camel_imapx_conn_manager_get_connection (camel-imapx-conn-manager.c:878) > by 0xFA2F36F: camel_imapx_store_ref_server (camel-imapx-store.c:2690) > by 0xFA0E879: imapx_synchronize_sync (camel-imapx-folder.c:1097) > by 0x312485B692: camel_folder_synchronize_sync (camel-folder.c:3623) > by 0x105346AF: refresh_folders_exec (mail-send-recv.c:1029) > by 0x3E3AA21EC6: mail_msg_proxy (mail-mt.c:373) > by 0x3F1A471147: g_thread_pool_thread_proxy (gthreadpool.c:307) > by 0x3F1A4707B4: g_thread_proxy (gthread.c:764) > by 0x3F17807529: start_thread (pthread_create.c:310) > by 0x3F17D0077C: clone (clone.S:109) > Address 0x31e90510 is 0 bytes inside a block of size 136 free'd > at 0x4A07CE9: free (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) > by 0x3F1A44F7FE: g_free (gmem.c:190) > by 0x3F1A466C43: g_slice_free1 (gslice.c:1112) > by 0x3E3444FE25: gdk_event_source_translate_event (gdkeventsource.c:221) > by 0x3E3444FE25: _gdk_x11_display_queue_events (gdkeventsource.c:338) > by 0x3E34426878: gdk_display_get_event (gdkdisplay.c:321) > by 0x3E3444FAD1: gdk_event_source_dispatch (gdkeventsource.c:360) > by 0x3F1A449AEA: g_main_dispatch (gmain.c:3111) > by 0x3F1A449AEA: g_main_context_dispatch (gmain.c:3710) > by 0x3F1A449E87: g_main_context_iterate.isra.29 (gmain.c:3781) > by 0x3F1A44A1B1: g_main_loop_run (gmain.c:3975) > by 0x3E337EBB34: gtk_main (gtkmain.c:1207) > by 0x403794: main (main.c:685)
Glad to hear that! I just reported Bug 741238, which also has many mentions of g_network_address_address_enumerator_next(), so it might well be the same problem.
*** Bug 697016 has been marked as a duplicate of this bug. ***
The related code significantly changed after the changes for bug #745545, for example the code from the initial report is completely gone, thus I'm closing this in a favour of those changes.