Ubuntu
telepathy-gabble package

telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()

Bug #1061034 reported by Vasilis Toumpakaris on 2012-10-03

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

Don't know

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: telepathy-gabble 0.16.1-2
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Oct 3 18:28:43 2012
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=el_GR.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

Vasilis Toumpakaris (toumbo) wrote on 2012-10-03:

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-03: 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.