Bug 821228
| Summary: | [abrt] Repeated threads with e_ews_connection_get_folder, e_book_backend_ews_authenticate_user | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||
| Component: | evolution-ews | Assignee: | Matthew Barnes <mbarnes> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | mbarnes, mcrha, pbrobinson | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:12dc6644b9c67161d83947710b2345f4407d9866 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-06-08 23:59:56 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Mikhail
2012-05-13 09:44:35 UTC
Created attachment 584123 [details]
File: backtrace
Created attachment 584124 [details]
File: maps
Created attachment 584125 [details]
File: dso_list
Created attachment 584126 [details]
File: build_ids
Thanks for a bug report. The backtrace shows that quite many threads are in authenticate phase against your EWS server, being after initial login phase and trying to receive default folders there. The "crashing" thread unfortunately doesn't show anything useful, it seems to be in idle, similar to other threads. Do you have any steps how to reproduce this crash, please? *** Bug 821314 has been marked as a duplicate of this bug. *** *** Bug 823263 has been marked as a duplicate of this bug. *** kill evolution-addressbook-factory when it hang CPU backtrace_rating: 4 Package: evolution-data-server-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Seems after logon, evolution-addressbook-factory couldn't get my exchange password (my exchange password is stored and evolution can get it) from password store and begins eat CPU resources, after i kill him with SEGV to get this backtrace. This problem related directly with broken GAL. *** Bug 824011 has been marked as a duplicate of this bug. *** *** Bug 821307 has been marked as a duplicate of this bug. *** *** Bug 825226 has been marked as a duplicate of this bug. *** *** Bug 825430 has been marked as a duplicate of this bug. *** *** Bug 825746 has been marked as a duplicate of this bug. *** *** Bug 826045 has been marked as a duplicate of this bug. *** *** Bug 826659 has been marked as a duplicate of this bug. *** *** Bug 826930 has been marked as a duplicate of this bug. *** *** Bug 827482 has been marked as a duplicate of this bug. *** *** Bug 827739 has been marked as a duplicate of this bug. *** I see similar behaviour with evolution-*-3.4.2, the addressbook factory tries to authenticate against ews server, but it fails, but instead of stopping it tries again and again, which leads to various issues, like account lock for Peter. I unpushed the 3.4.2 update from updates-testing too, and I suggest to downgrade to 3.4.1, which you can do with yum: $ yum downgrade evolution-* or by naming each evolution package on the yum's command line. I'm currently investigating what broke that it stopped working. I'm going to make this through upstream bug [1], and provide internal update of evolution-ews as 3.4.2-2. [1] https://bugzilla.gnome.org/show_bug.cgi?id=677398 evolution-mapi-3.4.2-1.fc17, evolution-data-server-3.4.2-1.fc17, evolution-3.4.2-1.fc17, gtkhtml3-4.4.2-1.fc17, evolution-ews-3.4.2-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-7850/evolution-ews-3.4.2-2.fc17,evolution-mapi-3.4.2-1.fc17,evolution-data-server-3.4.2-1.fc17,evolution-3.4.2-1.fc17,gtkhtml3-4.4.2-1.fc17 *** Bug 828133 has been marked as a duplicate of this bug. *** Package evolution-mapi-3.4.2-1.fc17, evolution-data-server-3.4.2-1.fc17, evolution-3.4.2-1.fc17, gtkhtml3-4.4.2-1.fc17, evolution-ews-3.4.2-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing evolution-mapi-3.4.2-1.fc17 evolution-data-server-3.4.2-1.fc17 evolution-3.4.2-1.fc17 gtkhtml3-4.4.2-1.fc17 evolution-ews-3.4.2-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7850/evolution-ews-3.4.2-2.fc17,evolution-mapi-3.4.2-1.fc17,evolution-data-server-3.4.2-1.fc17,evolution-3.4.2-1.fc17,gtkhtml3-4.4.2-1.fc17 then log in and leave karma (feedback). evolution-mapi-3.4.2-1.fc17, evolution-data-server-3.4.2-1.fc17, evolution-3.4.2-1.fc17, gtkhtml3-4.4.2-1.fc17, evolution-ews-3.4.2-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |