Gajim-devel April 2007

gajim-devel@gajim.org

10 participants
6 discussions

Re: [Gajim-devel] [patch] attach notification to systray
by Norbert Tretkowski 01 May '07

01 May '07

* Le Boulanger Yann wrote: > If some ppl want to test, here is the patch to apply. Any plans to include this patch in one of the next releases? Norbert

2 3

chatstate argument of MessageControl.get_tab_label
by Mikhail Gusarov 30 Apr '07

30 Apr '07

Hi. Is 'chatstate' argument of MessageControl.get_tab_label supposed to be used in future or it is just a leftover? I found no code which calls get_tab_label with explicit 'chatstate' argument. -- JID: dottedmag(a)jabber.dottedmag.net

2 1

Gajim on the cover of GNUzilla magazine
by Adrian C. 18 Apr '07

18 Apr '07

Hello, Gajim got a solid review (and even appeared on the cover :) in the last issue of GNUzilla magazine; which is a very popular free software zine on the teritory of former Yugoslavia. You can check it out here http://gnuzilla.fsnserbia.org/ Cheers, anrxc. -- JID:anrxc|sysphere|org | sysphere.org/~anrxc/

3 3

[PATCH] fix for bug #2824 remember history window dimensions
by John Kelly 16 Apr '07

16 Apr '07

Hi guys, This patch saves the history window size and position values to disk and loads them when the history window is shown. This is my first patch so any suggestions on how to improve it are welcome :) Regards, John

2 1

Re: [Gajim-devel] gajim 0.11 causes JID too long error in Wildfire server
by yann 09 Apr '07

09 Apr '07

Günter Dannoritzer a écrit : > yann wrote: >> Günter Dannoritzer a écrit : >>> Hi, >>> >>> When I log in with gajim (0.11) to a Wildfire server (3.2.4) I am >>> getting kicked out first and then the login happens a few seconds later. >>> >>> When looking in the log of the server, there is an entry that the JID is >>> too long. >>> >>> Anybody has experienced something similar? >>> >>> What is the limitation on the JID length? Is that a limitation of the >>> Wildfire server? >>> >>> I posted the full error message from the server below. >>> >>> Thanks for any help. >>> >>> Cheers, >>> >>> Guenter >>> >> I never heard such a problem. is you jid really long? > > Not that I know of. > >> what do Gajim logs show? (run gajim -v in a console to see them) >> > > I attached the log until the client was connected. > > This is a 0.11 client under Linux. > > It does not show any obvious errors to me, but I am not an expert. > > You can see that the client logs in two times. I did not find a reason > why it got disconnected after the first try. > > Cheers, > > Guenter > indeed in the middle of your log, gajim gets a </stream:stream> without any reason. This sounds like a server pb, as it work on other wildfire servers. Have you tried with other clients ? do you see something different in logs ? -- Yann

5 4

gajim 0.11 causes JID too long error in Wildfire server
by Günter Dannoritzer 02 Apr '07

02 Apr '07

Hi, When I log in with gajim (0.11) to a Wildfire server (3.2.4) I am getting kicked out first and then the login happens a few seconds later. When looking in the log of the server, there is an entry that the JID is too long. Anybody has experienced something similar? What is the limitation on the JID length? Is that a limitation of the Wildfire server? I posted the full error message from the server below. Thanks for any help. Cheers, Guenter ================================================================================================== 2007.04.01 13:04:41 [org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager$1$1.run(ProxyConnectionManager.java:110)] Error processing file transfer proxy connection java.io.IOException: Error reading Socks5 version and command at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager.processIncomingSocks5Message(ProxyConnectionManager.java:215) at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager.processConnection(ProxyConnectionManager.java:168) at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager.access$100(ProxyConnectionManager.java:39) at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager$1$1.run(ProxyConnectionManager.java:107) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 2007.04.01 13:04:41 [org.jivesoftware.wildfire.IQRouter.handle(IQRouter.java:341)] Could not route packet java.lang.IllegalArgumentException: Illegal JID: at org.xmpp.packet.JID.init(JID.java:384) at org.xmpp.packet.JID.<init>(JID.java:219) at org.jivesoftware.wildfire.filetransfer.proxy.FileTransferProxy.handleIQ(FileTransferProxy.java:126) at org.jivesoftware.wildfire.filetransfer.proxy.FileTransferProxy.process(FileTransferProxy.java:349) at org.jivesoftware.wildfire.IQRouter.handle(IQRouter.java:250) at org.jivesoftware.wildfire.IQRouter.route(IQRouter.java:104) at org.jivesoftware.wildfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:67) at org.jivesoftware.wildfire.net.StanzaHandler.processIQ(StanzaHandler.java:289) at org.jivesoftware.wildfire.net.ClientStanzaHandler.processIQ(ClientStanzaHandler.java:79) at org.jivesoftware.wildfire.net.StanzaHandler.process(StanzaHandler.java:254) at org.jivesoftware.wildfire.net.StanzaHandler.process(StanzaHandler.java:153) at org.jivesoftware.wildfire.nio.ConnectionHandler.messageReceived(ConnectionHandler.java:131) at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:54) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800) at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:62) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:200) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:54) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800) at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:266) at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:326) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.jivesoftware.stringprep.IDNAException: String too long. at org.jivesoftware.stringprep.IDNA.toASCII(IDNA.java:153) at org.jivesoftware.stringprep.IDNA.toASCII(IDNA.java:53) at org.xmpp.packet.JID.init(JID.java:355) ... 25 more

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Gajim-devel April 2007