Bug 39471

Summary:	Weird behaviour when chatting with contacts using Trillian
Product:	papyon	Reporter:	Maurizio <6tsukiyami9>
Component:	general	Assignee:	papyon-bugs
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	medium	CC:	6tsukiyami9
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	logs

Description Maurizio 2011-07-22 05:53:34 UTC

Created attachment 49426 [details]
logs

Hello,
first off I've been experiencing this issue using emesene2 (here's the bug track: https://github.com/emesene/emesene/issues/685#issuecomment-1630798 ).
The problem is the following: when chatting with a contact using Trillian (tested with 4.2 and latest) his avatar is not correctly retrieved, and although messages that ether of us sends are correctly received, I keep getting flooded with 'error sending message' error (it gets repeated every 2 seconds or so per message sent). This sometimes causes a program crash, but I don't know if that's because of papyon or emesene2.

I'm attaching 2 logs, one regarding the error message, and another regarding the crash.

Comment 1 Riccardo (c10ud) 2011-08-16 08:49:09 UTC

seems like Trillian tells us p2pv2 is supported but then they NAK our messages

Comment 2 Riccardo (c10ud) 2011-08-16 08:50:45 UTC

reading the log better actually shows that p2pv1 support is involved, and trillian NAKs every message

Comment 3 Louis-Francis Ratté-Boulianne 2011-08-16 08:54:43 UTC

I actually tried with Trillian 5.0 and everything seems to work great. Can you test with that version and tell me if the problem still occurs. Thanks

Comment 4 Maurizio 2011-08-16 10:38:01 UTC

This still seem to happen with Trillian 5.0 Build 34... It doesn't seem to happen at all during conversation with multiple people (not all of them use Trillian though), but it does still occur when talking with a single contact using Trillian, even if it's kind of random

Comment 5 Riccardo (c10ud) 2011-08-18 06:15:25 UTC

[15:13] <c10ud> lfrb, about the trillian "bug": when we leave a switchboard its state is set to ProtocolState.CLOSING..so why not ProtocolState.CLOSED? Also when papyon tries to reuse the switchboard in switchboard_manager, it doesn't set the state to ProtocolState.OPEN so here's the infinite looping
[15:13] <c10ud> This maybe a trillian bug because it's sending p2p data even if we sent OUT, but still papyon shouldn't break
[15:13] <c10ud> and i think this re-use thing has something wrong

Comment 6 Maurizio 2011-09-18 14:23:47 UTC

So... What's the status on this?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.