Bug 800480
| Summary: | [abrt] evolution-3.2.3-1.fc16: em_folder_tree_class_init: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | slalomnut | ||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | lucilanga, mbarnes, mcrha | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:c5dfd51ab500b7f6f6e8a95ef8f7a5fa79a79703 | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-02-13 16:40:32 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
slalomnut
2012-03-06 14:39:40 UTC
Created attachment 567975 [details]
File: gconf_subtree
Created attachment 567976 [details]
File: build_ids
Created attachment 567977 [details]
File: dso_list
Created attachment 567978 [details]
File: backtrace
Created attachment 567979 [details]
File: maps
Thanks for a bug report. The crash function is quite unexpected. If I read the backtrace properly, then this happens when you run evolution, with evolution-ews account being enabled. Is this reproducible on you machine, please? And if you run evolution from console, what is written there, please? I think the .xsession_errors output above is not complete. One test, if you can still reproduce it, does it help to run evolution in offline (evolution --offline) or even in another component (evolution -c tasks), or if you remove evolution-ews? I'm asking because I didn't see such crash in Fedora 16 yet. Milan, Console output: evolution GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. ** (evolution:31154): DEBUG: Loading Exchange EWS Plugin Construct the listener (evolution:31154): camel-CRITICAL **: camel_session_add_service: assertion `uri_string != NULL' failed Segmentation fault (core dumped) evolution --offline (evolution:31194): evolution-shell-CRITICAL **: shell_settings_pspec_for_key: assertion `schema_name != NULL' failed GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. ** (evolution:31194): DEBUG: Loading Exchange EWS Plugin Construct the listener (evolution:31194): camel-CRITICAL **: camel_session_add_service: assertion `uri_string != NULL' failed Segmentation fault (core dumped) evolution -c contacts Loads successfully in offline mode evolution -c contacts GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. ** (evolution:31291): DEBUG: Loading Exchange EWS Plugin Construct the listener ##Disabled the EWS account and switched to on-line and mail (evolution:31229): camel-CRITICAL **: camel_service_get_user_data_dir: assertion `CAMEL_IS_SERVICE (service)' failed Removed ews store summary: (evolution:31229): evolution-addressbook-CRITICAL **: e_book_shell_content_get_current_view: assertion `widget != NULL' failed (evolution:31229): eab-widgets-CRITICAL **: e_addressbook_view_get_model: assertion `E_IS_ADDRESSBOOK_VIEW (view)' failed (evolution:31229): eab-widgets-CRITICAL **: e_addressbook_view_get_selection_model: assertion `E_IS_ADDRESSBOOK_VIEW (view)' failed (evolution:31229): eab-widgets-CRITICAL **: e_addressbook_model_can_stop: assertion `E_IS_ADDRESSBOOK_MODEL (model)' failed (evolution:31229): eab-widgets-CRITICAL **: e_addressbook_model_get_editable: assertion `E_IS_ADDRESSBOOK_MODEL (model)' failed (evolution:31229): e-data-server-WARNING **: e_source_get_uri () called on source with no absolute URI! (evolution:31229): e-data-server-ui-CRITICAL **: e_credentials_authenticate_helper: assertion `e_credentials_has_key (credentials, E_CREDENTIALS_KEY_PROMPT_KEY)' failed (evolution:31229): camel-CRITICAL **: camel_session_add_service: assertion `uri_string != NULL' failed Segmentation fault (core dumped) ## Same results after removing the Exchange account from preferences. ## Remove packages Removed: evolution-ews.x86_64 0:3.2.3-1.fc16 evolution-exchange.x86_64 0:3.2.3-1.fc16 evolution -c contacts GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. (evolution:31386): camel-CRITICAL **: camel_session_add_service: assertion `uri_string != NULL' failed Segmentation fault (core dumped) Thanks for the update and testing. So it's not caused by evolution-ews or evolution-exchange. I also do not see anything I would expect from the console output, except of:
> GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will
> not be saved or shared with other applications.
Do you compile your own GLib, which is not compatible with built-in library? This message comes out when user compiles his own GLib.
No, I do not compile my own Glib. Installed packages: glib-1.2.10-35.fc16.x86_64 glib2-2.30.2-1.fc16.x86_64 glib2-2.30.2-1.fc16.i686 glibc-headers-2.14.90-24.fc16.6.x86_64 glibc-common-2.14.90-24.fc16.6.x86_64 glib2-devel-2.30.2-1.fc16.x86_64 glibc-devel-2.14.90-24.fc16.6.x86_64 glibc-2.14.90-24.fc16.6.i686 glibc-2.14.90-24.fc16.6.x86_64 OK, I just updated my system and I have the same version of glibc/glib2 packages as you, except of the
> glib-1.2.10-35.fc16.x86_64
which I do not have installed at all. I have
glib-networking-2.30.1-2.fc16.x86_64
only, which is used with libsoup.
I also have
dconf-0.10.0-1.fc16.x86_64
which is used in GSettings, providing correct backend there, which avoids the above warning about "memory backend".
I'm afraid that there is something wrong with your installation, which is causing this issue. I didn't see any such bug report before too, and the fedora 16 is out long enough to have it reported already, being it a generic bug. Still, I would like to know what is so different on your installation that it prevents evolution to run properly.
Well, out of curiosity, I did a yum reinstall on all installed evolution and it's back up. I haven't added the OWA module yet but fingers are crossed. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is 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" 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 Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |