Description of problem: Happened just after kernel update from 3.7.9, using yum distro-sync, which also stated you have a new mail in /var/spool/mail/[username]. After rebooting the system and going past the login screen, gnome crashed and i was returned to the login screen again. Version-Release number of selected component: evolution-data-server-3.6.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-source-registry crash_function: exit dso_list: executable: /usr/libexec/evolution-source-registry kernel: 3.8.1-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #2 exit at exit.c:99
Created attachment 708088 [details] File: backtrace
Created attachment 708089 [details] File: build_ids
Created attachment 708090 [details] File: cgroup
Created attachment 708091 [details] File: core_backtrace
Created attachment 708092 [details] File: environ
Created attachment 708093 [details] File: limits
Created attachment 708094 [details] File: maps
Created attachment 708095 [details] File: open_fds
Created attachment 708096 [details] File: proc_pid_status
Thanks for a bug report. The crashing thread doesn't show anything useful, unfortunately. Does it still crash for you? I guess the /usr/libexec/evolution-source-registry process claims something on console when this happens, if so, then it may help to identify the issue, unless it being caused by the update. The updates-testing contains evolution 3.6.4, which should be compiled against more recent kernel, thus if you could try to update to it, then it'll help. Please see the update [1] for the list of updated (and rebuilt) packages. [1] https://admin.fedoraproject.org/updates/FEDORA-2013-3530
It crashed just that once, after which i deleted the file in /var/spool/mail because it was annoying me.
It's weird. Even if you would have setup an email account which would read from /var/spool/mail/[user], then the evolution-source-registry doesn't access it, it does evolution itself.
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.