Gloox "onConnect" handler not called. Mint 32-only

Bug #1071416 reported by Jean-Christophe Lavoie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux Mint
New
Undecided
Unassigned

Bug Description

I do realize this is kinda tricky and probably won't found/reproduced/fixed but still... I could probably make a demo application during the weekend. It's probably a net package that has a bug somewhere...

1)Linux Mint 13 32bits MATE. Bug does not happen on Mint 64bits, Ubuntu 12.04 x64 nor Debian 6.0 32bits. . Tested on a clean VM of Mint on a Mac Laptop with g++,boost 1.51 and gloox as the only package manually installed

2) Make a program using Gloox XMPP library. On connection, onTLSConnect() is called, the programmer must then choose to accept or reject the certificate. In case of accept (return true), onConnect() is called and connection is establish.

3)onConnect() is never called. Using jabber.org servers, the connection is established but presence is not set to "available". Client is seen as offline but communication works. However, when using a custom ejabberd server, connection is not established and communication does not work. Authentification and stream do not return any error.

4)onConnect() is correctly called

5) Always. Only on Linux mint 32 bits.

description: updated
description: updated
summary: - Gloox "onConnect" handler not called. Mint-only
+ Gloox "onConnect" handler not called. Mint 32-only
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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