Bug 1037581

Summary: [abrt] evolution-3.10.2-2.fc20: gdk_x11_window_foreign_new_for_display: Process /usr/libexec/evolution/3.10/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ccecchi, lucilanga, mbarnes, mclasen, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/28a47ad84359cf25f9dd0b7936886af0bba81301
Whiteboard: abrt_hash:3fdccae5df47ff252ad7f8343cad16cdb59fe2f8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:22:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brian J. Murrell 2013-12-03 12:07:10 UTC
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

Comment 1 Brian J. Murrell 2013-12-03 12:07:17 UTC
Created attachment 832010 [details]
File: backtrace

Comment 2 Brian J. Murrell 2013-12-03 12:07:20 UTC
Created attachment 832011 [details]
File: cgroup

Comment 3 Brian J. Murrell 2013-12-03 12:07:23 UTC
Created attachment 832012 [details]
File: core_backtrace

Comment 4 Brian J. Murrell 2013-12-03 12:07:26 UTC
Created attachment 832013 [details]
File: dso_list

Comment 5 Brian J. Murrell 2013-12-03 12:07:29 UTC
Created attachment 832014 [details]
File: environ

Comment 6 Brian J. Murrell 2013-12-03 12:07:32 UTC
Created attachment 832015 [details]
File: exploitable

Comment 7 Brian J. Murrell 2013-12-03 12:07:35 UTC
Created attachment 832016 [details]
File: limits

Comment 8 Brian J. Murrell 2013-12-03 12:07:39 UTC
Created attachment 832017 [details]
File: maps

Comment 9 Brian J. Murrell 2013-12-03 12:07:42 UTC
Created attachment 832018 [details]
File: open_fds

Comment 10 Brian J. Murrell 2013-12-03 12:07:45 UTC
Created attachment 832019 [details]
File: proc_pid_status

Comment 11 Brian J. Murrell 2013-12-03 12:07:47 UTC
Created attachment 832020 [details]
File: var_log_messages

Comment 12 Brian J. Murrell 2013-12-11 16:23:06 UTC
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?

Comment 13 Milan Crha 2014-01-09 14:55:23 UTC
Let's try it.

Comment 14 Fedora End Of Life 2015-05-29 09:54:32 UTC
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.

Comment 15 Fedora End Of Life 2015-06-29 13:22:45 UTC
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.