Bug 1144771 - [abrt] geary: g_type_check_instance_is_fundamentally_a(): geary killed by SIGSEGV
Summary: [abrt] geary: g_type_check_instance_is_fundamentally_a(): geary killed by SIG...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: geary
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:e27e864638f3c268d622f494e4f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-20 15:27 UTC by Vadim Rutkovsky
Modified: 2015-12-02 16:18 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 03:53:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (61.42 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: cgroup (190 bytes, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: core_backtrace (3.97 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: dso_list (24.35 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: environ (1.46 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: exploitable (82 bytes, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: limits (1.29 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: maps (81.23 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: open_fds (1.41 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: proc_pid_status (937 bytes, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details
File: var_log_messages (5.78 KB, text/plain)
2014-09-20 15:27 UTC, Vadim Rutkovsky
no flags Details

Description Vadim Rutkovsky 2014-09-20 15:27:34 UTC
Version-Release number of selected component:
geary-0.7.1-1.fc21

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_is_fundamentally_a at gtype.c:3981
 #1 g_object_ref at gobject.c:3041
 #2 _g_object_ref0 at /usr/src/debug/geary-0.7.1/src/client/conversation-list/conversation-list-view.vala:38
 #3 conversation_list_view_get_adjustment at /usr/src/debug/geary-0.7.1/src/client/conversation-list/conversation-list-view.vala:142
 #4 conversation_list_view_on_conversations_added_began at /usr/src/debug/geary-0.7.1/src/client/conversation-list/conversation-list-view.vala:113
 #5 _conversation_list_view_on_conversations_added_began_conversation_list_store_conversations_added_began at /usr/src/debug/geary-0.7.1/src/client/conversation-list/conversation-list-view.vala:61
 #6 _g_closure_invoke_va at gclosure.c:831
 #8 g_signal_emit_by_name at gsignal.c:3405
 #9 conversation_list_store_on_conversations_added at /usr/src/debug/geary-0.7.1/src/client/conversation-list/conversation-list-store.vala:381
 #13 g_signal_emit_by_name at gsignal.c:3405

Comment 1 Vadim Rutkovsky 2014-09-20 15:27:38 UTC
Created attachment 939576 [details]
File: backtrace

Comment 2 Vadim Rutkovsky 2014-09-20 15:27:39 UTC
Created attachment 939577 [details]
File: cgroup

Comment 3 Vadim Rutkovsky 2014-09-20 15:27:40 UTC
Created attachment 939578 [details]
File: core_backtrace

Comment 4 Vadim Rutkovsky 2014-09-20 15:27:42 UTC
Created attachment 939579 [details]
File: dso_list

Comment 5 Vadim Rutkovsky 2014-09-20 15:27:43 UTC
Created attachment 939580 [details]
File: environ

Comment 6 Vadim Rutkovsky 2014-09-20 15:27:44 UTC
Created attachment 939581 [details]
File: exploitable

Comment 7 Vadim Rutkovsky 2014-09-20 15:27:45 UTC
Created attachment 939582 [details]
File: limits

Comment 8 Vadim Rutkovsky 2014-09-20 15:27:47 UTC
Created attachment 939583 [details]
File: maps

Comment 9 Vadim Rutkovsky 2014-09-20 15:27:48 UTC
Created attachment 939584 [details]
File: open_fds

Comment 10 Vadim Rutkovsky 2014-09-20 15:27:50 UTC
Created attachment 939585 [details]
File: proc_pid_status

Comment 11 Vadim Rutkovsky 2014-09-20 15:27:51 UTC
Created attachment 939586 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-11-04 15:08:54 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 13 Fedora End Of Life 2015-12-02 03:53:55 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.