Hide Forgot
Version-Release number of selected component: evolution-data-server-3.8.5-4.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 3 cmdline: /usr/libexec/evolution-addressbook-factory executable: /usr/libexec/evolution-addressbook-factory kernel: 3.11.1-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1001 var_log_messages: Sep 30 12:45:41 rubik abrt[7622]: Saved core dump of pid 1977 (/usr/libexec/evolution-addressbook-factory) to /var/tmp/abrt/ccpp-2013-09-30-12:45:39-1977 (110403584 bytes) Truncated backtrace: Thread no. 1 (6 frames) #0 ?? #1 ldap_op_finished at e-book-backend-ldap.c:1183 #2 e_book_backend_ldap_stop_view at e-book-backend-ldap.c:5074 #3 bookview_stop_thread at e-data-book-view.c:266 #4 g_thread_proxy at gthread.c:798 #6 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Created attachment 805766 [details] File: backtrace
Created attachment 805767 [details] File: cgroup
Created attachment 805768 [details] File: core_backtrace
Created attachment 805769 [details] File: dso_list
Created attachment 805770 [details] File: environ
Created attachment 805771 [details] File: exploitable
Created attachment 805772 [details] File: limits
Created attachment 805773 [details] File: maps
Created attachment 805774 [details] File: open_fds
Created attachment 805775 [details] File: proc_pid_status
Thanks for a bug report. It's weird, this is supposed to be fixed since 3.8.1, according to [1]. The backtrace says, on its first line, that the core file may not match executable file, which usually means that you updated the executable while the previous version was still running. Is it possible you updated 3.8.0 to 3.8.5? [1] https://bugzilla.gnome.org/show_bug.cgi?id=699448
I don't think so: $ rpm -q --last evolution-data-server evolution-data-server-3.8.5-4.fc19.x86_64 Thu 15 Aug 2013 14:04:00 BST I get that message even when running gdb manually against the core file from abrt.
I got this on F19 also.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.