Ubuntu
evolution package

evolution crashes with SIGSEGV in g_hash_table_lookup_node() when "evolution-indicator" package is installed

Bug #1725315 reported by John Mellor
84
This bug affects 16 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Every few minutes, evolution exits the desktop. Sometimes it will only stay up for seconds, and sometimes it exits in the first second. Occasionally it stays up for ~20 minutes. When it is running, it seems to function normally. This machine was upgraded from 17.04 (where Evolution was stable) to 17.10 release.

Apport crashdump analysis attached.

Looking at /var/log/syslog after one of these crashes, I see the following entries:

Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant
Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (254): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (287): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (300): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (417): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: segfault at 0 ip (null) sp 00007ffee4f96718 error 14 in evolution[557e54c52000+7000]

It is not clear that the first few syslog entries are related.

Running evolution with debugging enabled:
CAMEL_DEBUG=all evolution

I see the following output when the crash occurs:

###########
message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (<email address hidden> : Inbox) for expression:---(and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk")))) (and (and (match-all (not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") (user-flag "important")))) (match-all (not (or (= (user-tag "label") "work") (user-flag "$Labelwork") (user-flag "work")))) (match-all (not (or (= (user-tag "label") "personal") (user-flag "$Labelpersonal") (user-flag "personal")))) (match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") (user-flag "todo")))) (match-all (not (or (= (user-tag "label") "later") (user-flag "$Labellater") (user-flag "later")))))))---
   message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (<email address hidden> : Inbox) after tweak, hide_deleted:1, hide_junk:1
Segmentation fault (core dumped)

Not sure if I can provide further information. This crash is highly-repeatable, happening hundreds of times/day.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: evolution 3.26.1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 09:50:57 2017
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2017-05-31 (142 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: evolution -c current
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? ()
 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
 org_gnome_mail_new_notify () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
Title: evolution crashed with SIGSEGV in g_hash_table_lookup()
UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)
UserGroups: adm cdrom docker libvirt lpadmin plugdev sambashare sudo

Revision history for this message
John Mellor (john-mellor) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x7c, hash_table=0x557e5540cb60) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x557e5540cb60, key=key@entry=0x7c) at ../../../../glib/ghash.c:1153
 lookup_cached_xatom (atom=0x7c, display=0x557e553e5000) at ././gdk/x11/gdkproperty-x11.c:76
 gdk_x11_atom_to_xatom_for_display (display=0x557e553e5000, atom=0x7c) at ././gdk/x11/gdkproperty-x11.c:109

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
summary: - evolution crashed with SIGSEGV in g_hash_table_lookup()
+ evolution crashed with SIGSEGV in g_hash_table_lookup_node()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evolution (Ubuntu):
status: New → Confirmed
Revision history for this message
nikolaos aidinidis (nickaidin) wrote :

hi there. I don t know if it is the second number verification to blame. But my evolution did not synchronise with google server. After that it crashes. But synchronising with hotmail server was not an issue.

Revision history for this message
Rudolf Leitgeb (rudolf-leitgeb) wrote :

I have just one IMAP account set up on my evolution instance, and it is neither gmail nor yahoo. Yet I have this problem. If "second number verification" refers to two-factor authentication, then no, my email account does not use it.

Revision history for this message
José Dapena Paz (jdapena) wrote :

This only happens on gnome-shell on wayland mode. It is evolution indicator plugin. Unfortunately, even clicking on the checkbox to disable it (on the list of evolution plugins) crashes evolution.

Revision history for this message
José Dapena Paz (jdapena) wrote :

Workaround: uninstall evolution-indicator package.

Revision history for this message
Mauro Gaspari (ilvipero) wrote :

Per comment #9, I confirm it only happens on gnome-shell on wayland mode.
I tested thoroughly over the last few days and I did not experience a single crash on gnome-shell on Xorg.Once I switch back to gnome-shell on wayland, the frequent crashes start happening again.

Per comment #10, I tested the workaround: uninstall evolution-indicator package, and I confirm it works. No more evolution crashes on gnome-shell on wayland.

PS
I ran the tests mentioned above on 2 machines: on Virtualbox VM, and on Hardware. Same results on both.

Revision history for this message
Phil Boutros (philb61) wrote :

Thank you for this, José. My machines that were crashing had the evolution-indicator package installed, and the one that never crashed did not.

Hopefully, removing that package solves the issue.

Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

This still occurs in 18.04/bionic. The workaround of removing evolution-indicator also still works.

Revision history for this message
John Mellor (john-mellor) wrote :

Can this be marked as a blocking bug for Ubuntu 18.04, so that we can get this fixed as a priority?

Evolution is the normal and default Gnome email reader. Using other email clients is just a workaround. This bug does not occur in Fedora, CentOS or RedHat - just Ubuntu.

Andre Klapper (a9016009)
summary: - evolution crashed with SIGSEGV in g_hash_table_lookup_node()
+ evolution crashes with SIGSEGV in g_hash_table_lookup_node() when
+ "evolution-indicator" package is installed
Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

Still occurs in 18.10/cosmic (evolution 3.30.1-1build1, evolution-indicator 0.2.20-0ubuntu36).

Revision history for this message
Eric Levy (8mabmzqcnyc1g4i7tjyvuprzli-contact-clubl5mz6ldresgvtiayqw6wzb) wrote :

I see the same behavior. Ubuntu 18.10. Gnome Shell over Wayland. Evolution is unstable unless the "evolution-indicator" package is removed.

Is it possible to disable the package without uninstalling?

Revision history for this message
Enrik Berkhan (enrikb) wrote :

I reported the bug including a proposed fix on evolution-indicator: https://bugs.launchpad.net/evolution-indicator/+bug/1851036

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.