Description of problem: 1) open evolution 2) running with evolution-ews 3) try to send an email and recieved an error Version-Release number of selected component: evolution-3.6.3-2.fc18 Additional info: backtrace_rating: 3 cmdline: evolution executable: /usr/bin/evolution kernel: 3.8.2-206.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 ?? #7 gtk_dialog_run at gtkdialog.c:1110 #8 mailto_handler_prompt at evolution-mailto-handler.c:171 #9 mailto_handler_check at evolution-mailto-handler.c:206 #14 e_shell_event at e-shell.c:1864 Potential duplicate: bug 866207
Created attachment 711496 [details] File: backtrace
Created attachment 711497 [details] File: cgroup
Created attachment 711498 [details] File: core_backtrace
Created attachment 711499 [details] File: dso_list
Created attachment 711500 [details] File: environ
Created attachment 711501 [details] File: limits
Created attachment 711502 [details] File: maps
Created attachment 711503 [details] File: open_fds
Created attachment 711504 [details] File: proc_pid_status
Created attachment 711505 [details] File: var_log_messages
Thanks for a bug report. I see this crashed in a dbus-glib code, but evolution doesn't use this library directly, it might be introduced by other library, like GConf. Evolution used to have a special code for dbus-glib threading initialization, but it was removed since it moved away from GConf. There seem to be used a different library/plugin/code), which brings in a dependency on dbus-glib. I checked what brings it in and it's webkitgtk3, unfortunately. The best would be to port webkigtk to use GDBus, rather than dbus-glib, because GDBus is thread safe and adds more other advantages.
I would recommend that Evolution add the dbus-glib threading initialization back, until all the dependant libraries are ported away from dbus-glib.
(In reply to comment #11) > I checked what brings it in and it's webkitgtk3, unfortunately. It's not webkitgtk3 either, it seems to be geoclue that brings the dependency in. libwebkitgtk doesn't use any symbols from dbus-glib and the reason why it's linked with it is only because of geoclue. geoclue has Requires: dbus-glib-1 in its pkgconfig file, which causes everything that links with geoclue to also link with dbus-glib-1. Reassigning to geoclue.
(In reply to comment #13) > (In reply to comment #11) > > I checked what brings it in and it's webkitgtk3, unfortunately. > > It's not webkitgtk3 either, it seems to be geoclue that brings the > dependency in. > > libwebkitgtk doesn't use any symbols from dbus-glib and the reason why it's > linked with it is only because of geoclue. Thanks for more detailed search. I didn't look on symbol usages, I used only ldd to check for libraries.
I know Bastien (cc:ed) was working on a new version of geoclue to deal with this (amongst other issues) but I've no idea what the status of that effort is.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.