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

Bug #1284116 reported by Mark Murphy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

Experienced after logging in to my account from another account.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution-data-server 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CurrentDesktop: Unity
Date: Mon Feb 24 13:30:15 2014
ExecutablePath: /usr/lib/evolution/evolution-source-registry
InstallationDate: Installed on 2013-07-01 (237 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
ProcCmdline: /usr/lib/evolution/evolution-source-registry
SegvAnalysis:
 Segfault happened at: 0xb71d72ee <g_slice_alloc+158>: mov (%edi),%edx
 PC (0xb71d72ee) ok
 source "(%edi)" (0x000000b4) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_bytes_new_with_free_func () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_bytes_new_take () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_bytes_new () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to trusty on 2014-01-29 (26 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mark Murphy (mokmeister) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1195662, 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.

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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