Ubuntu
telepathy-gabble package

telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()

Bug #1132181 reported by Tiago Carrondo on 2013-02-23

This bug report is a duplicate of: Bug #915015: telepathy-gabble crashed with signal 5 in g_return_if_fail_warning(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	telepathy-gabble (Ubuntu)	New	Undecided	Unassigned

Bug Description

after deactivating network in network manager

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: telepathy-gabble 0.16.1-2
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sat Feb 23 17:41:07 2013
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationDate: Installed on 2013-01-23 (30 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130114)
MarkForUpload: True
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANGUAGE=pt:pt_BR:en
LANG=pt_PT.UTF-8
Signal: 5
SourcePackage: telepathy-gabble
StacktraceTop:
g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_hash_table_foreach () from /lib/i386-linux-gnu/libglib-2.0.so.0
?? ()
g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
?? ()
Title: telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Tiago Carrondo (tcarrondo) wrote on 2013-02-23:

Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-02-23: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #915015, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.