evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

[Thomas A. F. Thorne]

Yesterday I closed Evolution down. This morning when I got back into the office and login to my Ubuntu machine (after leaving it locked overnight) I get a report about a problem. I was prompted about bug #1195662 and bug #1235177 being similar, however neither of those seem to have had any activity in a year. Also this has now occurred on a more recent version of Ubuntu so I felt fresh diagnostic files may be helpful. Please make this bug a duplicate of something if it looks to be one.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution-data-server 3.10.4-0ubuntu1.5
ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-56-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec 18 04:21:15 2015
ExecutablePath: /usr/lib/evolution/evolution-source-registry
InstallationDate: Installed on 2015-03-12 (280 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: /usr/lib/evolution/evolution-source-registry
SegvAnalysis:
 Segfault happened at: 0x7fb9d8a1628a <g_slice_alloc+154>: mov 0x8(%rdx),%rbx
 PC (0x7fb9d8a1628a) ok
 source "0x8(%rdx)" (0x7fb9b802159008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_dict_entry () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1279108, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Thomas A. F. Thorne (tafthorne)]

I have added a comment to each of the similar bugs (bug #1195662 and bug #1235177) mentioning that they may also be a bug of bug #1279108. Sadly bug #1279108 "Cannot be found" by me, which is usually a sign that it has been left marked as Private. There ends my possible involvement in the diagnosis unless someone reading this can evaluate bug #1279108 and either state that this bug is not a duplicate of it or remove the Private stamp from bug #1279108.

[Thomas A. F. Thorne (tafthorne)]

Weirdly the top of this bug report currently states it is a duplicate of nothing. I take it that is a launchpad but, as other bits of launchpad manage to state it is a duplicate of bug #1279108 (which I don't seem to have permissions to view). I will search for or raise a launchpad bug about this.

[Thomas A. F. Thorne (tafthorne)]

I could not find an open bug for launchpad that seemed to describe the problem with the blank after the This bug report is a duplicate of: message so I have raised https://bugs.launchpad.net/launchpad/+bug/1527529 (which I guess might be bug #1527529 if bug numbers are universal between projects and packages.

[Thomas A. F. Thorne (tafthorne)]

So I have tripped over the same problem again, but this time only Bug #1195662 and Bug #1235177 were offered as suggestions. Bug #1527495 that I raised a while ago was not seen as a likely similarity.

It seems that I am able to periodically reproduce a problem, whether it is one of the three bugs listed above or the possibly mythical bug #1279108 I cannot say. However if there are any investigative steps I can take or work arounds to try please do get in touch.

[Thomas A. F. Thorne (tafthorne)]

Seen again today. As before #1195662 and Bug #1235177 were offered as suggestions but bug #1279108 was not. Can anyone that is able to view all four of these bugs make a judgement on whether the first two are in fact a duplicate of the latter as this one is?