Bug 1032461

Summary: [abrt] evolution-3.8.5-2.fc19: gdk_property_change: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Oren Oichman <two.oes>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fa89f5fd5f64467544221b37f49aceddaa9cfba0
Whiteboard: abrt_hash:b0c183a326deb381cff61e7a32d802badee9ad19
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:19:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 Oren Oichman 2013-11-20 09:21:55 UTC 
Description of problem:
I had created a now appointment and the evolution crashed

Version-Release number of selected component:
evolution-3.8.5-2.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        evolution --online
crash_function: gdk_property_change
executable:     /usr/bin/evolution
kernel:         3.11.8-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 gdk_property_change at gdkwindow.c:11582
 #1 _gtk_selection_request at gtkselection.c:2453
 #2 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
 #3 _g_closure_invoke_va at gclosure.c:840
 #6 gtk_widget_event_internal at gtkwidget.c:6722
 #7 gtk_widget_event at gtkwidget.c:6379
 #8 gtk_main_do_event at gtkmain.c:1649
 #14 gtk_main at gtkmain.c:1156

Potential duplicate: bug 841326
Comment 1 Oren Oichman 2013-11-20 09:22:05 UTC 
Created attachment 826473 [details]
File: backtrace
Comment 2 Oren Oichman 2013-11-20 09:22:09 UTC 
Created attachment 826474 [details]
File: cgroup
Comment 3 Oren Oichman 2013-11-20 09:22:19 UTC 
Created attachment 826475 [details]
File: core_backtrace
Comment 4 Oren Oichman 2013-11-20 09:22:25 UTC 
Created attachment 826476 [details]
File: dso_list
Comment 5 Oren Oichman 2013-11-20 09:22:30 UTC 
Created attachment 826477 [details]
File: environ
Comment 6 Oren Oichman 2013-11-20 09:22:34 UTC 
Created attachment 826478 [details]
File: exploitable
Comment 7 Oren Oichman 2013-11-20 09:22:38 UTC 
Created attachment 826479 [details]
File: limits
Comment 8 Oren Oichman 2013-11-20 09:22:42 UTC 
Created attachment 826480 [details]
File: maps
Comment 9 Oren Oichman 2013-11-20 09:22:46 UTC 
Created attachment 826481 [details]
File: open_fds
Comment 10 Oren Oichman 2013-11-20 09:22:50 UTC 
Created attachment 826482 [details]
File: proc_pid_status
Comment 11 Oren Oichman 2013-11-20 09:22:53 UTC 
Created attachment 826483 [details]
File: var_log_messages
Comment 12 Milan Crha 2013-11-20 11:45:10 UTC 
Thanks for a bug report. I see ABRT found a similar crash from 3.4.4, which is quite long time ago, and I'm not aware of any similar bug report in current upstream stable version, which is 3.10.2, it'll be part of Fedora 20. I'd suggest to try the 3.10.x version, once the Fedora 20 is out, at least in a virtual machine. I do not expect you can reproduce this reliably when you create a new appointment, can you?
Comment 13 Fedora Admin XMLRPC Client 2014-09-04 14:29:24 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 14 Fedora End Of Life 2015-01-09 20:38:39 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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-02-17 19:19:14 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.