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

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

Bug Description

I have nothing to say just a crash on quantal

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.6.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Tue Oct 30 09:35:47 2012
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2011-07-21 (466 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
SegvAnalysis:
 Segfault happened at: 0x7f7a63528d26: movzbl (%rsi),%ecx
 PC (0x7f7a63528d26) ok
 source "(%rsi)" (0x00000003) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcontacts.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evolution-calendar-factory crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to quantal on 2012-10-10 (19 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare vboxusers wireshark

Revision history for this message
zzecool (zzecool) 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 #1064452, 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-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.