Bug 1026192

Summary: [abrt] telepathy-gabble-0.18.1-1.fc21: g_source_remove: Process /usr/libexec/telepathy-gabble was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: telepathy-gabbleAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bdpepple, sander, satellitgo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3e40b6be9fc4bb3e4d148887a3889ab52e4e293d
Whiteboard: abrt_hash:87012f813c4c064376e0998f46fec9d115fc64b0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:33:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Nicolas Mailhot 2013-11-04 07:14:05 UTC
Version-Release number of selected component:
telepathy-gabble-0.18.1-1.fc21

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: g_source_remove
executable:     /usr/libexec/telepathy-gabble
kernel:         3.12.0-0.rc7.git4.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #2 g_source_remove at gmain.c:2209
 #3 tp_run_connection_manager at run.c:301
 #4 gabble_main at gabble.c:177
 #6 _start

Comment 1 Nicolas Mailhot 2013-11-04 07:14:13 UTC
Created attachment 818944 [details]
File: backtrace

Comment 2 Nicolas Mailhot 2013-11-04 07:14:16 UTC
Created attachment 818945 [details]
File: cgroup

Comment 3 Nicolas Mailhot 2013-11-04 07:14:19 UTC
Created attachment 818946 [details]
File: core_backtrace

Comment 4 Nicolas Mailhot 2013-11-04 07:14:22 UTC
Created attachment 818947 [details]
File: dso_list

Comment 5 Nicolas Mailhot 2013-11-04 07:14:25 UTC
Created attachment 818948 [details]
File: environ

Comment 6 Nicolas Mailhot 2013-11-04 07:14:28 UTC
Created attachment 818949 [details]
File: limits

Comment 7 Nicolas Mailhot 2013-11-04 07:14:32 UTC
Created attachment 818950 [details]
File: maps

Comment 8 Nicolas Mailhot 2013-11-04 07:14:34 UTC
Created attachment 818951 [details]
File: open_fds

Comment 9 Nicolas Mailhot 2013-11-04 07:14:38 UTC
Created attachment 818952 [details]
File: proc_pid_status

Comment 10 Nicolas Mailhot 2013-11-04 07:14:41 UTC
Created attachment 818953 [details]
File: var_log_messages

Comment 11 satellitgo 2014-01-01 03:58:31 UTC
f21 (rawhide) desktop live install 20131203 (koji) with sugar-desktop and sugar-runner

Comment 12 satellitgo 2014-02-18 01:28:05 UTC
occurred on first start of sugar-runner (sugar 0.100) in f21 (rawhide) koji 20140216 x86_64 in MATE install to HD

Comment 13 Jaroslav Reznik 2015-03-03 15:11:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 14 Fedora End Of Life 2016-07-19 10:33:10 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.