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

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

Bug Description

This crash was reported on startup; I've got no idea when it was triggered, or what triggered it.

Here's hoping for a nice retrace!

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.4.3-1
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
ApportVersion: 2.2.3-0ubuntu6
Architecture: amd64
Date: Thu Jun 21 10:23:15 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120521)
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
SegvAnalysis:
 Segfault happened at: 0x7fc9ad12896e: mov 0x8(%rax),%rdi
 PC (0x7fc9ad12896e) ok
 source "0x8(%rax)" (0xaaaaaaaaaaaaaab2) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcontacts.so
 g_cclosure_marshal_VOID__BOXEDv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () 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
Title: evolution-calendar-factory crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXEDv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Chris Halse Rogers (raof) 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 #1015794, 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.

tags: removed: need-amd64-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.