telepathy-gabble crashed with signal 5 in IA__g_return_if_fail_warning()

Bug #198704 reported by Scott James Remnant (Canonical)
86
This bug affects 16 people
Affects Status Importance Assigned to Milestone
loudmouth (Ubuntu)
Fix Released
Medium
Laurent Bigonville

Bug Description

Binary package hint: telepathy-gabble

Happens every time I login to Jabber

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Mar 5 11:15:14 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
Package: telepathy-gabble 0.7.2-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
Signal: 5
SourcePackage: telepathy-gabble
StacktraceTop:
 IA__g_return_if_fail_warning (log_domain=0x0,
 lm_message_node_get_child ()
 ?? () from /usr/lib/libloudmouth-1.so.0
 ?? ()
Title: telepathy-gabble crashed with signal 5 in IA__g_return_if_fail_warning()
Uname: Linux 2.6.24-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_return_if_fail_warning (log_domain=0x0,
lm_message_node_get_child (node=0x0,
connection_message_queue_cb (queue=0x80c8ff8,
message_queue_dispatch_func (source=0x80c9aa0, callback=0,
IA__g_main_context_dispatch (context=0x80b8f58)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in telepathy-gabble:
importance: Undecided → Medium
Revision history for this message
Guillaume Desmottes (cassidy) wrote :

Could you provide Gabble log with GABBLE_DEBUG=all and LM_DEBUG=net please?
See http://telepathy.freedesktop.org/wiki/Debugging for explanations.

Revision history for this message
Senko Rasic (senko) wrote :

This is due to incorrect stream:error stanza parsing in Loudmouth.
The issue has been fixed in upstream Loudmouth 1.3.4 release.

Details in git commit:
http://github.com/hallski/loudmouth/commit/fce1ac2fbd251ac8a3b9c73532312c54ad454a26

Changed in telepathy-gabble:
assignee: nobody → bigon
status: New → Fix Committed
Changed in loudmouth:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.