Bug 1268976

Summary: [abrt] telepathy-salut: _g_log_abort(): telepathy-salut killed by SIGTRAP
Product: [Fedora] Fedora Reporter: rh <robinhaern>
Component: telepathy-salutAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: apo, bdpepple, john.j5live
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/476edc87cd98f4fbef1d4ec8553c3a36102db8f4
Whiteboard: abrt_hash:e85507e4fd666159457d64fbda3ddb08c881ac35;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:07:00 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: build_ids
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 rh 2015-10-05 19:24:37 UTC 
Version-Release number of selected component:
telepathy-salut-0.8.1-7.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-salut
crash_function: _g_log_abort
executable:     /usr/libexec/telepathy-salut
global_pid:     3441
kernel:         4.1.8-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _g_log_abort at gmessages.c:315
 #3 g_source_remove at gmain.c:2252
 #4 gibber_r_multicast_causal_transport_dispose at gibber-r-multicast-causal-transport.c:290
 #6 gibber_r_multicast_transport_dispose at gibber-r-multicast-transport.c:337
 #8 gibber_muc_connection_dispose at gibber-muc-connection.c:232
 #10 salut_muc_channel_dispose at muc-channel.c:724
 #12 g_value_unset at gvalue.c:272
 #13 g_value_array_free at gvaluearray.c:169
 #14 invoke_object_method at dbus-gobject.c:2049
 #15 object_registration_message at dbus-gobject.c:2168
Comment 1 rh 2015-10-05 19:24:41 UTC 
Created attachment 1080027 [details]
File: backtrace
Comment 2 rh 2015-10-05 19:24:43 UTC 
Created attachment 1080028 [details]
File: build_ids
Comment 3 rh 2015-10-05 19:24:44 UTC 
Created attachment 1080029 [details]
File: cgroup
Comment 4 rh 2015-10-05 19:24:46 UTC 
Created attachment 1080030 [details]
File: core_backtrace
Comment 5 rh 2015-10-05 19:24:47 UTC 
Created attachment 1080031 [details]
File: dso_list
Comment 6 rh 2015-10-05 19:24:48 UTC 
Created attachment 1080032 [details]
File: environ
Comment 7 rh 2015-10-05 19:24:50 UTC 
Created attachment 1080033 [details]
File: limits
Comment 8 rh 2015-10-05 19:24:52 UTC 
Created attachment 1080034 [details]
File: maps
Comment 9 rh 2015-10-05 19:24:53 UTC 
Created attachment 1080035 [details]
File: mountinfo
Comment 10 rh 2015-10-05 19:24:54 UTC 
Created attachment 1080036 [details]
File: namespaces
Comment 11 rh 2015-10-05 19:24:56 UTC 
Created attachment 1080037 [details]
File: open_fds
Comment 12 rh 2015-10-05 19:24:57 UTC 
Created attachment 1080038 [details]
File: proc_pid_status
Comment 13 rh 2015-10-05 19:24:59 UTC 
Created attachment 1080039 [details]
File: var_log_messages
Comment 14 Fedora End Of Life 2016-07-19 18:07:00 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.