evolution-calendar-factory crashed with SIGSEGV in g_type_check_instance()

Bug #1194079 reported by Michael Blennerhassett
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crashed after login, possibly after network timeout

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.8.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
Uname: Linux 3.9.0-6-generic x86_64
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
Date: Mon Jun 24 20:14:37 2013
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2013-06-22 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f754883f7b9 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7f754883f7b9) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: evolution-calendar-factory crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Michael Blennerhassett (mjblenner) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x7f75181a2320) at /build/buildd/glib2.0-2.37.1/./gobject/gtype.c:4082
 g_signal_emit_valist (instance=0x7f75181a2320, signal_id=100, detail=0, var_args=var_args@entry=0x7f74faffc278) at /build/buildd/glib2.0-2.37.1/./gobject/gsignal.c:3105
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.37.1/./gobject/gsignal.c:3382
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7f74faffc5d0, fn=0x7f75463450b0 <re_emit_socket_client_event>, rvalue=0x7f74faffc500, avalue=avalue@entry=0x7f74faffc480) at ../src/x86/ffi64.c:522

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution-data-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in evolution-data-server (Ubuntu):
status: New → Confirmed
Revision history for this message
berken agaoglu (berken) wrote :

evolution-addressbook-factory crashed with SIGSEGV in g_type_check_instance()

I had this crash report right after I had enabled virtual machine option in the BIOS.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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