| Summary: | [abrt] evolution-2.28.3-24.el6: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Red Hat Case Diagnostics <case-diagnostics> | ||||||
| Component: | evolution-mapi | Assignee: | Matthew Barnes <mbarnes> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.0 | CC: | mcrha, swaikar, tpelka, vgaikwad | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:183f8355e8be9ddb06d4a8c5030dfea046ff9584 | ||||||||
| Fixed In Version: | evolution-mapi-0.32.2-1.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-11-21 05:03:09 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | 883017 | ||||||||
| Bug Blocks: | 782183, 960054 | ||||||||
| Attachments: |
|
||||||||
|
Description
Red Hat Case Diagnostics
2011-07-22 00:41:40 UTC
Created attachment 514601 [details]
File: backtrace
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Created attachment 514660 [details]
Backtrace, Dissassembly
Thanks for a bug report. The detailed backtrace reads:
#0 0x00007f6ed8794bcd in get_SPropValue (lpProps=0x7f6e97fffdd0, ulPropTag=923205663) at libmapi/property.c:109
#1 0x00007f6ed8a9d1a7 in exchange_mapi_util_find_SPropVal_array_propval (values=0x7f6e97fffdd0, proptag=923205663)
at exchange-mapi-utils.c:147
#2 0x00007f6ed8cb248d in mapi_folder_item_to_msg (folder=0x1860f00, uid=0x7f6eb5a495cf "8E67AA8A17000004DE23437D6B000001", ex=
0x7f6eb5a26478) at camel-mapi-folder.c:1643
#3 mapi_folder_get_message (folder=0x1860f00, uid=0x7f6eb5a495cf "8E67AA8A17000004DE23437D6B000001", ex=0x7f6eb5a26478)
at camel-mapi-folder.c:1775
#4 0x000000338422f10c in camel_folder_get_message (folder=0x1860f00, uid=0x7f6eb5a495cf "8E67AA8A17000004DE23437D6B000001", ex=
0x7f6eb5a26478) at camel-folder.c:1121
#5 0x00000033842366e9 in offline_downsync_sync (session=<value optimized out>, mm=0x7f6eb5a26460) at camel-offline-folder.c:114
#6 0x000000338424314b in session_thread_proxy (msg=0x7f6eb5a26460, session=0x10a8c30) at camel-session.c:592
#7 0x000000397826360b in g_thread_pool_thread_proxy (data=<value optimized out>) at gthreadpool.c:265
#8 0x0000003978262074 in g_thread_create_proxy (data=0x7f6eb5a51350) at gthread.c:635
which seams to be related to part of an upstream bug [1]. Similar change is included in a patch for bug #711784, thus if you could give a try to the test package from there then it may show us whether that change will help here too. Thanks in advance.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=608771
Hi, I refer upstream bugzilla #608771. As evolution-2.28 does not have notification code then how can I create package for this issue?? The test build from bug #711784 is still alive [1], just pick the architecture you are using. With the upstream comment about no notification code, I'm not sure what exactly I meant with it, and how much it correlates with bug #711784. If test package from there will help you, then I'll mark this as a duplicate of it. [1] https://brewweb.devel.redhat.com/taskinfo?taskID=3513084 (In reply to comment #9) > The test build from bug #711784 is still alive [1], just pick the architecture > you are using. With the upstream comment about no notification code, I'm not > sure what exactly I meant with it, and how much it correlates with bug #711784. > If test package from there will help you, then I'll mark this as a duplicate of > it. > > [1] https://brewweb.devel.redhat.com/taskinfo?taskID=3513084 I went through the link but I did not get download link anywhere. I'm rebuilding the package [1], I just realized that the build is gone, while I thought it's not. I'm sorry for not making sure. I rechecked line numbers from the detailed backtrace and this happens while working with message attachments, thus the above mentioned bug may address this particular crash too. In case you get crashes with rebuilt package, please update the backtrace (if not the same, then rather in a new bug report), to track it properly. Thanks in advance and once again, I'm sorry for confusion I caused here. [1] https://brewweb.devel.redhat.com/taskinfo?taskID=3583639 No problem with backtrace it is same. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Hello, I can see that bug is marked for inclusion in 6.5 When can it gets ack? I'm sorry, I miss conclusions on this bug. Is it fixed by changes from bug #711784, or it is not? The upstream patch (see comment #7) is part of 0.32.2, thus I'm making this a dependency of the rebase bug. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1540.html |