Bug 1134054 - [abrt] evolution: gtk_widget_get_toplevel(): evolution killed by SIGSEGV
Summary: [abrt] evolution: gtk_widget_get_toplevel(): evolution killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:a17728ad8d394977a4414d550c7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-26 17:47 UTC by andrew
Modified: 2015-06-29 22:16 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:16:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (57.97 KB, text/plain)
2014-08-26 17:47 UTC, andrew
no flags Details
File: cgroup (180 bytes, text/plain)
2014-08-26 17:47 UTC, andrew
no flags Details
File: core_backtrace (33.54 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: dso_list (25.12 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: environ (1.42 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: exploitable (82 bytes, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: limits (1.29 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: maps (122.99 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: open_fds (2.98 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: proc_pid_status (943 bytes, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details
File: var_log_messages (3.09 KB, text/plain)
2014-08-26 17:48 UTC, andrew
no flags Details

Description andrew 2014-08-26 17:47:56 UTC
Version-Release number of selected component:
evolution-3.10.4-3.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        evolution
crash_function: gtk_widget_get_toplevel
executable:     /usr/bin/evolution
kernel:         3.15.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 gtk_widget_get_toplevel at gtkwidget.c:10738
 #1 gtk_widget_hide at gtkwidget.c:4418
 #2 g_cclosure_marshal_VOID__INTv at gmarshal.c:410
 #3 _g_closure_invoke_va at gclosure.c:840
 #6 alert_timeout_cb at e-alert.c:433
 #12 gtk_main at gtkmain.c:1158

Potential duplicate: bug 888963

Comment 1 andrew 2014-08-26 17:47:58 UTC
Created attachment 931058 [details]
File: backtrace

Comment 2 andrew 2014-08-26 17:47:59 UTC
Created attachment 931059 [details]
File: cgroup

Comment 3 andrew 2014-08-26 17:48:00 UTC
Created attachment 931060 [details]
File: core_backtrace

Comment 4 andrew 2014-08-26 17:48:01 UTC
Created attachment 931061 [details]
File: dso_list

Comment 5 andrew 2014-08-26 17:48:02 UTC
Created attachment 931062 [details]
File: environ

Comment 6 andrew 2014-08-26 17:48:02 UTC
Created attachment 931063 [details]
File: exploitable

Comment 7 andrew 2014-08-26 17:48:03 UTC
Created attachment 931064 [details]
File: limits

Comment 8 andrew 2014-08-26 17:48:04 UTC
Created attachment 931065 [details]
File: maps

Comment 9 andrew 2014-08-26 17:48:05 UTC
Created attachment 931066 [details]
File: open_fds

Comment 10 andrew 2014-08-26 17:48:05 UTC
Created attachment 931067 [details]
File: proc_pid_status

Comment 11 andrew 2014-08-26 17:48:06 UTC
Created attachment 931068 [details]
File: var_log_messages

Comment 12 Milan Crha 2014-09-01 10:32:47 UTC
Thanks for a bug report. Do you have any details about what you were doing when the crash happened, please? Ideally any steps for a reproducer would be helpful. I'm not able to guess much from the backtrace, the only thing I see is that crash happened when some information was going to be hidden in the UI, but nothing more.

Comment 13 andrew 2014-09-02 15:13:57 UTC
Milan nothing extraordinary. I think it's the best to wait until the other your worked on makes it way to the repo so i can install it. And if the same problem repeats itself, then we can work on it.

Comment 14 Fedora Admin XMLRPC Client 2014-09-04 14:30:43 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 15 Fedora End Of Life 2015-05-29 12:44:14 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 16 Fedora End Of Life 2015-06-29 22:16:10 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.


Note You need to log in before you can comment on or make changes to this bug.