emesene not login to hotmail and messenger for the conversation. emesene 1.6.3 is no longer stable since the MSN protocols have changed and the project was abandoned emesene 1.6.3 EPR give space to the new version emesene 2 will be stable soon. But now how do you go? Reproducible: Always Steps to Reproduce: 1. run emesene 2. login a messenger chat 3. infinity login Actual Results: not login a messenger
http://blog.emesene.org/2011/11/emesene-is-unable-to-connect.html
run emesene and output error Traceback (most recent call last): File "./emesene", line 32, in <module> import emesene File "/root/emesene/emesene/emesene.py", line 73, in <module> import e3 File "/root/emesene/emesene/e3/__init__.py", line 1, in <module> from base import * File "/root/emesene/emesene/e3/base/__init__.py", line 24, in <module> from Worker import Worker File "/root/emesene/emesene/e3/base/Worker.py", line 25, in <module> import Logger File "/root/emesene/emesene/e3/base/Logger.py", line 24, in <module> import sqlite3.dbapi2 as sqlite ImportError: No module named sqlite3.dbapi2
Else in the blog a comment that says: cesar_suarez said... Emesene 1.6.3 fixed uploaded to GitHub :D. I've only replaced contacts.msn.com to local-bay.contacts.msn.com and it works. https://github.com/csuarez/emesene-1.6.3-fixed I tried this release changed, but not working.
It would have been better to submit a patch instead of the entire sources. It will take a while (if I find the motivation to uncover his patch) before I commit a fixed version to tree.
Created attachment 292427 [details, diff] Updated msn server address I wrote a patch against the emesene-1.6.3 tarball based on the recommended changes from upstream. It emerges fine against an updated ebuild and my emesene (amd64) can connect correctly once again!
Created attachment 292431 [details] Updated ebuild to go with server change patch
This is now fixed in latest 2.X version. It is a bit unlikely for 1.6.3 to work again in the near(far) future
then delete it, or enter the unstable version 1.6.3 to version 2.11.11 with 2.11.11 since it is the only one for now "working" even if still in development.
(In reply to comment #5) > Created attachment 292427 [details, diff] [details, diff] > Updated msn server address > > I wrote a patch against the emesene-1.6.3 tarball based on the recommended > changes from upstream. It emerges fine against an updated ebuild and my emesene > (amd64) can connect correctly once again! Why is this patch not applied to 1.6.x?
@king: No I wont delete 1.6.X. Someone may write a patch in the future @Pacho: Because this patch does not work for everyone. It may work for your account today but your account may move to a different server tomorrow and the "redirection bug" will hit your account as well.
Anyway, I wouldn't consider this as FIXED leaving current stable version completely broken and without any testing version (that could move to stable in the near future) available. Pointing people to use hardmasked version doesn't look a fix to me and maybe current stable should also be hardmasked as it simply doesn't work
papyon upstream solved this with: http://cgit.freedesktop.org/papyon/commit/?id=ae863cd1e869a22f6b1bcfee93d4b801fd8e2200 That looks to redirect people to https://omega.contacts.msn.com/ I am not too familiar with emesene code (I am a simple user of it), but looks like it's using its own papyon copy and, then, it's not inheritting this fix included in latest papyon version by upstream. On the other hand, per last Markos comment I am unsure if papyon fix will help for all users :-/, even if upstream thinks it's the correct fix.
Well, and I have just seen upstream fix in emesene2 consist on updating to latest papyon code and, then, that fix looks as "flaky" as the way pointed by attached patch for emesene-1: https://github.com/emesene/emesene/issues/915
What exactly would be the ideal solution for you guys? I will unmask emesene:2 very soon. If someone wants to put some effort patching emesene-1.6.X to use system's papyon instead of the bundled one then feel free to do so. Right now I am not sure what would be an appropriate solution since emesene:2 is in a development state and emesene:1 is broken and abandoned.
Scratch my last comment. It seems emesene:1 is not using the papyon code. The latest emesene:2 fixes the problem which is now in ~arch tree.
I would adapt attached patch to this bug report to use the same msn server now used by upstream papyon :-/
Like I said it is not just a matter of $HOST url address. Have a look on the kmess patch ( applied in 2.0.6-r3 ). The solution is far more complex
I think the solution might be: to enter the emesene 1.6.3 to 2.11.11 in unstable branch so you can also use emesene 2 and also help the development of the same.
(In reply to comment #16) > I would adapt attached patch to this bug report to use the same msn server now > used by upstream papyon :-/ For now I am using successfully attached patch for 1.6.3 as, for now, it works for me and emesene2 looks to have a lot of problems to import my old account from emesene1 :(
So I would say to apply the patch as soon as possible and return emesene v1.6.3 stable and functioning.
(In reply to comment #20) > So I would say to apply the patch as soon as possible and return emesene v1.6.3 > stable and functioning. Yes, I would patch it also even keeping this bug opened (as the fix is not completely ok), since, without patching, it doesn't work at all.
(In reply to comment #21) > (In reply to comment #20) > > So I would say to apply the patch as soon as possible and return emesene v1.6.3 > > stable and functioning. > > Yes, I would patch it also even keeping this bug opened (as the fix is not > completely ok), since, without patching, it doesn't work at all. correct, we just have to wait to apply the patch emesene1 and restore the well functioning of the same.
+*emesene-1.6.3-r1 (28 Nov 2011) + + 28 Nov 2011; Pacho Ramos <pacho@gentoo.org> +emesene-1.6.3-r1.ebuild, + +files/emesene-1.6.3-update-servers.patch: + Workaround problems to connect to servers, bug #389955 +
emesene-1.6.3-r1 Stable x86
