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

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

Bug Description

This happend just after starting 13.10.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.8.5-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Thu Oct 3 12:08:16 2013
ExecutablePath: /usr/lib/evolution/evolution-source-registry
InstallationDate: Installed on 2012-08-07 (422 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-source-registry
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=de_DE
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb718eb1e <g_slice_alloc+158>: mov (%edi),%edx
 PC (0xb718eb1e) 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 saucy on 2013-09-29 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Laryllan (laryllan) 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.