Summary: | net-im/imcom disconnects when attempting to get protocol transport | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitrij D. Czarkoff <czarkoff> |
Component: | Current packages | Assignee: | Thomas Raschbacher <lordvan> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | CC: | lordvan, peter |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://imcom.im/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dmitrij D. Czarkoff
2006-04-30 01:50:02 UTC
Sorry, I've missed the important data: ddc@czarkerlaptop ~ $ emerge -pv imcom && imcom -v These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-im/imcom-1.34 0 kB Total size of downloads: 0 kB IMCom version 1.33 patch 1 is released under the BSD license. See LICENSE for details Written by Casey Crabb (JID: airog@floobin.cx) Usage: imcom [opts] -d --debug Turn on debugging -p --profile Use the specified profile Example: imcom -p floobin.cx Example: imcom Example: imcom -d i'll ask the author about this next time i talk to him ... Re-assigning wrt Bug 155664. I am not autherized to watch the referenced bug. :-( will have a look.. ignore reference bug ... ;) works here - on my own server. maybe the server is sending something invalid for some reason? (In reply to comment #6) > works here - on my own server. > maybe the server is sending something invalid for some reason? Don't think so: I tried several servers in Russia, all top known and used in a region. Any other JID-capable IM-client could connect, but imcom couldn't... Still it's not supported anymore by the author, no successor appeared, so it looks like this bug could be simply ignored, the imcom could be retired from portage tree. hmm darn i like the client ;) I am currently considering just removing the whole package from the tree since the maintainer dropped it a long time ago. Although someone else seems to have picked it back up. I'm trying to contact him now since there haven't been any updates since 2010.. (In reply to comment #0) > This happens when I try to connect protocol transport jn any server with IMCom. > > IMCom> /agenthelp icq.jabber.ru > Beginning the registration process. Requesting required information. > IMCom> Receive Exception > > Traceback (most recent call last): > File "/usr/share/imcom/JabberHandler.py", line 1281, in run > self.feed(data) > File "/usr/share/imcom/JabberHandler.py", line 1242, in feed > self.parser.Parse(data,0) > File "/usr/share/imcom/JabberHandler.py", line 663, in endElement > self.imcom.handleIQ(self.elementStack.pop()) > File "/usr/share/imcom/IMCom.py", line 1712, in handleIQ > self.handleIQRegister(iq) > File "/usr/share/imcom/IMCom.py", line 2055, in handleIQRegister > self.cbHandleIQError(iq.ffrom, iq.error.code, iq.error.text) > AttributeError: ErrorTag instance has no attribute 'text' > a is exceptions.AttributeError > b is ErrorTag instance has no attribute 'text' > > Server Disconnected us at 12:30:10 New maintainer here. I use transports locally without problems too. jabberd-1.4 server, with at the moment only an MSN transport. Although the backtrace has some detail, it would be nice to have complete protocol dumps for a working and a failing case; ie. from another client and from imcom. I realize it has been a while. I am closing this as NEEDINFO. @Dmitrij please re-open with info the maintainer requested if you still have the problem (and [want to] use imcom) |