Closed michael-borkowski closed 10 years ago
There two potential reasons for this behavior:
1 - You may have a jabber client reconnecting automatically, so your session is dropped.
2 - It could also be related to #973 and as the preferences are stored to the XMPP server...
So you can try to get logged on with another user to see if it occurs again. And also disable the welcome view pluggin on you client to reset the settings from the interface. (There is also a way to reset the presences directly on the XMPP server but I don't remember how :p)
Disabling the GeneralWelcomeView in modules.plist fixed the issue. The welcome screen still shows (or is that something different?) though, but at least there is no signout. Was that the correct way to disable the module? Also, re-enabling the module causes the error to re-appear. I suspect that if I build the client from sources, the newest fix will be included and this error doesn't occur anymore?
Thank you for your support! I love the fact that I'm able to use Archipel again :-)
You're right, you can download niglies as building the UI is not simple. Give a try but it seems that the building bot is not working well for now.
@michael-borkowski Just note that nightlies don't currently build. #1028
My web client instance signs out of the XMPP server (almost) immediately after login. Here is what happens:
I have already reinstalled and reconfigured my XMPP server and have no contacts. I have also tried the archipel-hosted web client with the same result.
The strange thing is that Archipel has already worked. Not sure what is causing the problems now.
Here is what I saw in the ejabberd logs:
Maybe the "replaced session for..." has got something to do with it?
What can I provide to further diagnose the problem?
Thanks for the work, I really liked Archipel so far until this issue occured!