| Summary: | [abrt] evolution-data-server-2.32.1-1.fc14: nbtlist_handler: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Barnsley <barnsls> | ||||
| Component: | samba4 | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | mbarnes, mcrha, ssorce | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:e882b882b830ad0a83eab8e4d713dfff8615fba4 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-16 14:16:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Steve Barnsley
2011-03-06 17:57:34 UTC
Created attachment 482533 [details]
File: backtrace
Thanks for a bug report. Is it anyhow reproducible, please? It seems to me, on the first look, like some network issue happened and then the application crashed. It's crashing in a library used by evolution-mapi. Could you try to run evolution from console and see whether there will be any messages/warnings printed just before the crash and if so, then paste them here, please? Thanks in advance. Yes, it is reproducible. 1) Connect to VPN 2) Start Evolution (mapi, pop and imap services active) 3) Exit Evolution 4) Close VPN connection 5) Log out of Gnome 6) Log into Gnome 7) data-server crashes This is a typical usage pattern for me - simpler scenarios may also cause the error but I haven't had time to test them (busy at work). Also, I should point out that I'm using evolution-mapi 2.32.2 from the test repository in conjunction with the rest of evolution at the 2.32.1 release (the later mapi version fixes a major problem with using exchange calendars). Hope this helps. Thanks for the update. I just pushed the rest of 2.32.2 update to stable, so you may get other evolution-related packages soon, though this is not related to the issue. From the above I understand that re-login into evolution with evolution-mapi and newly unreachable exchange server, which was reachable in the previous login/run, causes this crash. I'm not aware of anything available on MAPI side for the connection issue like this, thus I'm moving this to samba4, which is, from my point of view, in a role of connection "manager" for libmapi, to get their opinion on this. No problem. Just to be clear, the crash occurs while logging into Gnome (probably when the clock applet in the panel starts) not when starting evolution. After the crash (which is only apparent because abrt throws a wobbler) evolution starts up just fine if you choose to run it. Backtrace analysis found this bug to be similar to bug #565862 from component evolution. You might want to check that bug for additional information. This comment is automatically generated. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |