[Rtcomm] [Rtcomm] [Bug 3455] telepathy-gabble deadlooping

From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.org
Date: Sat Feb 21 10:34:34 EET 2009
https://bugs.maemo.org/show_bug.cgi?id=3455





------- Comment #10 from maemo at subs.maneos.org  2009-02-21 10:34 GMT+3 -------
(In reply to comment #9)
> maybe you could try rebuilding the Fremantle package for Diablo and check
> whether it helps with the issue?

It depends on glib >= 2.16 so seems like more trouble than it's worth.  I did
try the Fremantle libloudmouth just in case but it made no difference. 
Telepathy-gabble itself is missing from both Fremantle pre-alphas.

If you have access to a complete enough XMPP stack on Fremantle feel free to
use home.maneos.org:5224 for testing (resolves as both A & AAAA and returns
RST).

Some more findings:

- Fiddling with /etc/gai.conf to make the resolver prefer IPv4 addresses made
no difference.
- Running with MALLOC_CHECK_=2 doesn't do or report anything new.
- When running with GABBLE_DEBUG=connection (or =all) telepathy-gabble exits
normally after failing to connect.

The last one suggests a somewhat acceptable (well, better than the alternative)
kludge, ie changing
/usr/share/dbus-1/services/org.freedesktop.Telepathy.ConnectionManager.gabble.service
to:

[D-BUS Service]
Name=org.freedesktop.Telepathy.ConnectionManager.gabble
Exec=/bin/sh -c "GABBLE_DEBUG=connection /usr/bin/telepathy-gabble"

BTW, are you able to comment on kernel-side Fremantle IPv6 support?  It's
currently disabled in the pre-alphas, but after bug 356 I'd expect it at least
to be built as a module.  If it's loaded by default or built into the kernel
then at least this flavour of the bug goes away.

Cedric: can you still reproduce your strace results with 5.2008.43-7?


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=3455
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the Rtcomm mailing list