Version-Release number of selected component: evolution-3.4.4-1.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: evolution crash_function: g_logv kernel: 3.5.2-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 g_logv at gmessages.h : #2 g_wakeup_new at gwakeup.c : #3 g_cancellable_make_pollfd at gcancellable.c : #4 g_cancellable_get_fd at gcancellable.c : #5 cs_waitinfo at camel-net-utils.c : #6 camel_getaddrinfo at camel-net-utils.c : #7 tcp_stream_raw_connect at camel-tcp-stream-raw.c : #8 tcp_stream_ssl_connect at camel-tcp-stream-ssl.c : #9 camel_tcp_stream_connect at camel-tcp-stream.c : #10 network_service_connect_sync at camel-network-service.c
Created attachment 625925 [details] File: core_backtrace
Created attachment 625926 [details] File: environ
Created attachment 625927 [details] File: limits
Created attachment 625928 [details] File: backtrace
Created attachment 625929 [details] File: cgroup
Created attachment 625930 [details] File: maps
Created attachment 625931 [details] File: dso_list
Created attachment 625932 [details] File: var_log_messages
Created attachment 625933 [details] File: open_fds
Thanks for a bug report. There is a similar bug report filled upstream [1], but it lacks a reproducer, especially the message which g_wakeup_new() tried to print on console, with a reason of the abort. Are you able to reproduce this when you run evolution from console, please? Maybe it depends on the time evolution is running, thus just run evolution and left it running until this happens? [1] https://bugzilla.gnome.org/show_bug.cgi?id=661182
*** Bug 865775 has been marked as a duplicate of this bug. ***
I still have the full abrt info for this crash. Unfortunately the crash was with evolution-3.4.4-1.fc17 and I now have evolution-3.4.4-2.fc17 installed, so gdb won't let me interrogate the core file. Any other solution than to just wait for another occurrence? Oh wait. evolution stdout/stderr should be in .xsession-errors. Or so I thought it would be. Grepping for "Creating pipes for GWakeup" didn't yield anything.
Thanks for the update. You are right with the .xsession-errors, but it's cleared each login (it I recall correctly). ABRT reports try to read it too, but for crashes like this, when the error is just printed into console and application aborts, the ABRT does not catch it, as it reads .xsession-errors too early. Thus the option is, unfortunately, to just wait until it exhibits itself again, keeping evolution running form a console/terminal.
when click reply on a opened message. evolution is retrieving mail, and some a I/O error is reporting. backtrace_rating: 4 Package: evolution-3.4.4-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.