After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 652693 - [abrt] evolution-data-server-3.0.2-1.fc15: cal_backend_finalize: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT)
[abrt] evolution-data-server-3.0.2-1.fc15: cal_backend_finalize: Process /usr...
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.0.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-06-16 07:23 UTC by Milan Crha
Modified: 2012-09-04 19:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2011-06-16 07:23:20 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=713397

abrt version: 2.0.1
architecture:   x86_64
cmdline:        /usr/libexec/e-calendar-factory
component:      evolution-data-server
crash_function: cal_backend_finalize
executable:     /usr/libexec/e-calendar-factory
kernel:         2.6.38.7-30.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        evolution-data-server-3.0.2-1.fc15

Core was generated by `/usr/libexec/e-calendar-factory'.
Program terminated with signal 6, Aborted.

+ Trace 227493







Comment 1


Milan Crha





          2012-09-04 19:09:38 UTC
        



Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.