Bug 1058386 - [abrt] telepathy-gabble: g_return_if_fail_warning(): telepathy-gabble killed by SIGTRAP
Summary: [abrt] telepathy-gabble: g_return_if_fail_warning(): telepathy-gabble killed ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-gabble
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7d1f183face36b2113bbd909df2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-27 17:20 UTC by Robert Hancock
Modified: 2015-06-29 14:47 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:47:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (32.37 KB, text/plain)
2014-01-27 17:20 UTC, Robert Hancock
no flags Details
File: cgroup (172 bytes, text/plain)
2014-01-27 17:20 UTC, Robert Hancock
no flags Details
File: core_backtrace (15.92 KB, text/plain)
2014-01-27 17:20 UTC, Robert Hancock
no flags Details
File: dso_list (5.35 KB, text/plain)
2014-01-27 17:20 UTC, Robert Hancock
no flags Details
File: environ (971 bytes, text/plain)
2014-01-27 17:20 UTC, Robert Hancock
no flags Details
File: limits (1.29 KB, text/plain)
2014-01-27 17:20 UTC, Robert Hancock
no flags Details
File: maps (32.42 KB, text/plain)
2014-01-27 17:21 UTC, Robert Hancock
no flags Details
File: open_fds (689 bytes, text/plain)
2014-01-27 17:21 UTC, Robert Hancock
no flags Details
File: proc_pid_status (942 bytes, text/plain)
2014-01-27 17:21 UTC, Robert Hancock
no flags Details
File: var_log_messages (217 bytes, text/plain)
2014-01-27 17:21 UTC, Robert Hancock
no flags Details

Description Robert Hancock 2014-01-27 17:20:43 UTC
Version-Release number of selected component:
telepathy-gabble-0.18.1-1.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: g_return_if_fail_warning
executable:     /usr/libexec/telepathy-gabble
kernel:         3.12.8-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_return_if_fail_warning at gmessages.c:1034
 #3 g_hash_table_foreach at ghash.c:1529
 #4 gabble_vcard_manager_dispose at vcard-manager.c:562
 #6 gabble_connection_dispose at connection.c:1279
 #10 tp_base_connection_finish_shutdown at base-connection.c:2896
 #11 closed_cb at connection.c:2319
 #12 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #13 complete_close at wocky-c2s-porter.c:815
 #14 remote_connection_closed at wocky-c2s-porter.c:1229
 #15 stanza_received_cb at wocky-c2s-porter.c:1326

Potential duplicate: bug 783706

Comment 1 Robert Hancock 2014-01-27 17:20:47 UTC
Created attachment 856153 [details]
File: backtrace

Comment 2 Robert Hancock 2014-01-27 17:20:49 UTC
Created attachment 856154 [details]
File: cgroup

Comment 3 Robert Hancock 2014-01-27 17:20:52 UTC
Created attachment 856155 [details]
File: core_backtrace

Comment 4 Robert Hancock 2014-01-27 17:20:54 UTC
Created attachment 856156 [details]
File: dso_list

Comment 5 Robert Hancock 2014-01-27 17:20:56 UTC
Created attachment 856157 [details]
File: environ

Comment 6 Robert Hancock 2014-01-27 17:20:59 UTC
Created attachment 856158 [details]
File: limits

Comment 7 Robert Hancock 2014-01-27 17:21:01 UTC
Created attachment 856159 [details]
File: maps

Comment 8 Robert Hancock 2014-01-27 17:21:03 UTC
Created attachment 856160 [details]
File: open_fds

Comment 9 Robert Hancock 2014-01-27 17:21:05 UTC
Created attachment 856161 [details]
File: proc_pid_status

Comment 10 Robert Hancock 2014-01-27 17:21:07 UTC
Created attachment 856162 [details]
File: var_log_messages

Comment 11 Diego 2014-10-22 08:10:42 UTC
Another user experienced a similar problem:

This happened when my internet connection dropped for a while

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: g_return_if_fail_warning
executable:     /usr/libexec/telepathy-gabble
kernel:         3.16.6-200.fc20.x86_64
package:        telepathy-gabble-0.18.2-1.fc20
reason:         telepathy-gabble killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 12 Fedora End Of Life 2015-05-29 10:42:05 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 13 Fedora End Of Life 2015-06-29 14:47:48 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.