e-calendar-factory crashed accepting ICS invite
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-data-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The crash accepting invites occurs frequently, but not always.
Re-accepting invites that have previously been accepted in evolution (and then retained) can be used to generate the bug on subsequent evolution loads.
The root cause appears to be how threads to Gconf are initiated, which will eventually be resolved with a move to Gsettings in the future (3.6) per the upstream developer comments.
https:/
For now, the upstream patch resolves the issue by using dbus-glib instead.
I re-posted this because the original bug seems to have been moved to fix-released based on the recent upstream activities (RESOLVED, FIXED) which I am not sure is correct.
https:/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: evolution-
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sat Mar 17 00:35:16 2012
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x7f6c0f4b26e0: movl $0xffffffff,
PC (0x7f6c0f4b26e0) ok
source "$0xffffffff" ok
destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evolution-
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: e-calendar-factory crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-13 (3 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video
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 #847578, 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.