Bug 1255635

Summary: [abrt] empathy: g_hash_table_lookup(): empathy-chat killed by SIGABRT
Product: [Fedora] Fedora Reporter: Matthias Scholz <matthias.scholz>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bdpepple, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/aeedf3703f95e5a6a37a1ddf9b2f3e47c76d7098
Whiteboard: abrt_hash:0d8b418147f29601aeca7abe785047d2fb076eef
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:36:25 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Matthias Scholz 2015-08-21 08:54:19 UTC
Version-Release number of selected component:
empathy-3.12.10-2.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/empathy-chat
crash_function: g_hash_table_lookup
executable:     /usr/libexec/empathy-chat
global_pid:     4097
kernel:         4.1.4-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 g_hash_table_lookup at /lib64/libglib-2.0.so.0
 #5 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:163
 #7 empathy_move_to_window_desktop at empathy-ui-utils.c:1209
 #9 empathy_chat_window_present_chat at empathy-chat-window.c:2862
 #10 handle_channels at empathy-chat-manager.c:224
 #13 handle_channels_context_prepare_cb at /lib64/libtelepathy-glib.so.0
 #14 g_simple_async_result_complete at /lib64/libgio-2.0.so.0
 #15 context_check_prepare at /lib64/libtelepathy-glib.so.0
 #16 hcc_channel_prepare_cb at /lib64/libtelepathy-glib.so.0
 #17 g_simple_async_result_complete at /lib64/libgio-2.0.so.0

Comment 1 Matthias Scholz 2015-08-21 08:54:22 UTC
Created attachment 1065484 [details]
File: backtrace

Comment 2 Matthias Scholz 2015-08-21 08:54:23 UTC
Created attachment 1065485 [details]
File: cgroup

Comment 3 Matthias Scholz 2015-08-21 08:54:24 UTC
Created attachment 1065487 [details]
File: core_backtrace

Comment 4 Matthias Scholz 2015-08-21 08:54:26 UTC
Created attachment 1065489 [details]
File: dso_list

Comment 5 Matthias Scholz 2015-08-21 08:54:27 UTC
Created attachment 1065491 [details]
File: environ

Comment 6 Matthias Scholz 2015-08-21 08:54:31 UTC
Created attachment 1065495 [details]
File: limits

Comment 7 Matthias Scholz 2015-08-21 08:54:33 UTC
Created attachment 1065497 [details]
File: maps

Comment 8 Matthias Scholz 2015-08-21 08:54:34 UTC
Created attachment 1065499 [details]
File: mountinfo

Comment 9 Matthias Scholz 2015-08-21 08:54:35 UTC
Created attachment 1065501 [details]
File: namespaces

Comment 10 Matthias Scholz 2015-08-21 08:54:37 UTC
Created attachment 1065503 [details]
File: open_fds

Comment 11 Matthias Scholz 2015-08-21 08:54:38 UTC
Created attachment 1065504 [details]
File: proc_pid_status

Comment 12 Matthias Scholz 2015-08-21 08:54:39 UTC
Created attachment 1065505 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2016-07-19 17:36:25 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.