Hide Forgot
Description of problem: I wish this had a good stack trace in it for you but the lack of useful stack trace is being caused by bug 1036918.1036918 Version-Release number of selected component: evolution-3.10.2-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/evolution/3.10/evolution-alarm-notify crash_function: gdk_x11_window_foreign_new_for_display executable: /usr/libexec/evolution/3.10/evolution-alarm-notify kernel: 3.11.9-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (9 frames) #0 gdk_x11_window_foreign_new_for_display at /lib64/libgdk-3.so.0 #1 gdk_x11_display_translate_event at /lib64/libgdk-3.so.0 #2 _gdk_x11_event_translator_translate at /lib64/libgdk-3.so.0 #3 _gdk_x11_display_queue_events at /lib64/libgdk-3.so.0 #4 gdk_display_get_event at /lib64/libgdk-3.so.0 #5 gdk_event_source_dispatch at /lib64/libgdk-3.so.0 #7 g_main_context_iterate.isra.24 at /lib64/libglib-2.0.so.0 #8 g_main_context_iteration at /lib64/libglib-2.0.so.0 #9 g_application_run at /lib64/libgio-2.0.so.0
Created attachment 832010 [details] File: backtrace
Created attachment 832011 [details] File: cgroup
Created attachment 832012 [details] File: core_backtrace
Created attachment 832013 [details] File: dso_list
Created attachment 832014 [details] File: environ
Created attachment 832015 [details] File: exploitable
Created attachment 832016 [details] File: limits
Created attachment 832017 [details] File: maps
Created attachment 832018 [details] File: open_fds
Created attachment 832019 [details] File: proc_pid_status
Created attachment 832020 [details] File: var_log_messages
Realizing that this is a bug in GTK, I wonder if this is of any help: https://mail.gnome.org/archives/commits-list/2013-November/msg06825.html Maybe can we get this in front of the Fedora GTK maintainer's eyes?
Let's try it.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.