+ What will happen to pecan then?
UNOFFICIAL Adium with msnp15 testing
Re: UNOFFICIAL Adium with msnp15 testing
Perfect!! does it mean fast filetransfers? handwriting? custom emots sending?
+ What will happen to pecan then?

+ What will happen to pecan then?
Re: UNOFFICIAL Adium with msnp15 testing
no, no, yes but this part doesn't have a ui in Adium yet.markes wrote:Perfect!! does it mean fast filetransfers? handwriting? custom emots sending?
+ What will happen to pecan then?
It will probably continue to be developed and it's not sure that Adium will drop it.
Re: UNOFFICIAL Adium with msnp15 testing
Hello,
I have random crash with latest builds... someone else could report similar issues?
In the last lines of debug log there isn't nothing relevant ... however this is an example of a debug log (last lines) suddently after a crash:
http://pastebin.com/m107f6ae7
If I could help you more, just tell me what shoud I do...
I have random crash with latest builds... someone else could report similar issues?
In the last lines of debug log there isn't nothing relevant ... however this is an example of a debug log (last lines) suddently after a crash:
http://pastebin.com/m107f6ae7
If I could help you more, just tell me what shoud I do...
Re: UNOFFICIAL Adium with msnp15 testing
Don't see anything weird in your log really. It might be a crash error that's fixed now and will be in my next build.alexit84 wrote:Hello,
I have random crash with latest builds... someone else could report similar issues?
In the last lines of debug log there isn't nothing relevant ... however this is an example of a debug log (last lines) suddently after a crash:
http://pastebin.com/m107f6ae7
If I could help you more, just tell me what shoud I do...
Re: UNOFFICIAL Adium with msnp15 testing
Ok, I will wait for it.Dimmuxx wrote:Don't see anything weird in your log really. It might be a crash error that's fixed now and will be in my next build.alexit84 wrote:Hello,
I have random crash with latest builds... someone else could report similar issues?
In the last lines of debug log there isn't nothing relevant ... however this is an example of a debug log (last lines) suddently after a crash:
http://pastebin.com/m107f6ae7
If I could help you more, just tell me what shoud I do...
Meanwhile, this is an adium crash report... maybe could help you:
http://pastebin.com/m7b3158c5
Now, the last line of the debug window befor crash report:
Code: Select all
18:59:01: (Libpurple: blist) Updating buddy status for **********@gmail.com (MSN)Re: UNOFFICIAL Adium with msnp15 testing
Evan is looking for opinions if msnp15 should be included in 1.3 or not. So if you want to see it in 1.3 then you should say so and why you think it should.
http://adiumx.com/pipermail/adium-devl_ ... 05335.html
I will probably make a new and maybe last build later this day with a lot of fixes.
Edit: msnp15 won't be in Adium 1.3 so this isn't needed any longer.
http://adiumx.com/pipermail/adium-devl_ ... 05335.html
I will probably make a new and maybe last build later this day with a lot of fixes.
Edit: msnp15 won't be in Adium 1.3 so this isn't needed any longer.
Last edited by Dimmuxx on Wed Jul 16, 2008 2:53 am, edited 1 time in total.
-
hippy dave
- Muffin
- Posts: 49
- Joined: Wed Sep 12, 2007 2:49 am
Re: UNOFFICIAL Adium with msnp15 testing
maybe worth making a thread for that here? i'll sign up to adium-devl if i have to, but i'd rather not if it would be equally effective for evan to read my opinion hereDimmuxx wrote:Evan is looking for opinions if msnp15 should be included in 1.3 or not. So if you want to see it in 1.3 then you should say so and why you think it should.
http://adiumx.com/pipermail/adium-devl_ ... 05335.html
Re: UNOFFICIAL Adium with msnp15 testing
You don't need to sign up to write an email to the list. 
Re: UNOFFICIAL Adium with msnp15 testing
Yeah, you can send mail to the devel-list without joining it. Joining it is just if you wanna recieve all emails that gets sent to it.
-
hippy dave
- Muffin
- Posts: 49
- Joined: Wed Sep 12, 2007 2:49 am
Re: UNOFFICIAL Adium with msnp15 testing
ah ok thanks 
Re: UNOFFICIAL Adium with msnp15 testing
Build 24342 aka "hopefully my last build" is out and it pretty much fixes all the reported bugs and a lot of bugs that haven't been reported or listed here.
So enjoy it and lets hope this is my last build and that 1.3b8 will be msnp15!
So enjoy it and lets hope this is my last build and that 1.3b8 will be msnp15!
Re: UNOFFICIAL Adium with msnp15 testing
Thank you for your effort! 
Re: UNOFFICIAL Adium with msnp15 testing
First time posting in this thread, but I've been using your builds since they've come out. (and visionkrew's builds before that)
I also thank you for your time and efforts.
Hat's off to you! (and visionkrew as well)
I also thank you for your time and efforts.
Hat's off to you! (and visionkrew as well)
Re: UNOFFICIAL Adium with msnp15 testing
I have a new bug with the last build when trying to send an offline message (i keep the original message so you can see it's size. Here is the debug log:
Code: Select all
12:30:14: (Libpurple: msn) send IM {Comme t'es partie comme une voleuse sans rien dire!} to xxxxxxx@hotmail.com
12:30:14: (Libpurple: msn) prepare to send offline Message
12:30:14: (Libpurple: msn) Sending OIM: Comme t'es partie comme une voleuse sans rien dire!
12:30:14: (Libpurple: msn) No lock key challenge, waiting for SOAP Fault and Resend
12:30:14: (Libpurple: msn) Encoding OIM Message...
12:30:14: (Libpurple: msn) Encoded base64 body:{Q29tbWUgdCdlcyBwYXJ0aWUgY29tbWUgdW5lIHZvbGV1c2Ugc2FucyByaWVuIGRpcmUh}Re: UNOFFICIAL Adium with msnp15 testing
You always get a SOAP fault the first time you send an OIM after logging in this is because you don't have the lock key yet. This doesn't matter though since it just resends the message again and the next time you send an OIM you will have the lock key unless it's expired in which case the resending happens again.neckaros wrote:I have a new bug with the last build when trying to send an offline message (i keep the original message so you can see it's size. Here is the debug log:Code: Select all
12:30:14: (Libpurple: msn) send IM {Comme t'es partie comme une voleuse sans rien dire!} to xxxxxxx@hotmail.com 12:30:14: (Libpurple: msn) prepare to send offline Message 12:30:14: (Libpurple: msn) Sending OIM: Comme t'es partie comme une voleuse sans rien dire! 12:30:14: (Libpurple: msn) No lock key challenge, waiting for SOAP Fault and Resend 12:30:14: (Libpurple: msn) Encoding OIM Message... 12:30:14: (Libpurple: msn) Encoded base64 body:{Q29tbWUgdCdlcyBwYXJ0aWUgY29tbWUgdW5lIHZvbGV1c2Ugc2FucyByaWVuIGRpcmUh}
Unless some other real error occurred later this is nothing to worry about. Did it report an error to you?
-
supertoom2
- Harmless
- Posts: 3
- Joined: Sun Oct 29, 2006 12:35 pm
Re: UNOFFICIAL Adium with msnp15 testing
I get the same error log and Adium crashes when trying to send an offline message... (latest build)Dimmuxx wrote:You always get a SOAP fault the first time you send an OIM after logging in this is because you don't have the lock key yet. This doesn't matter though since it just resends the message again and the next time you send an OIM you will have the lock key unless it's expired in which case the resending happens again.neckaros wrote:I have a new bug with the last build when trying to send an offline message (i keep the original message so you can see it's size. Here is the debug log:Code: Select all
12:30:14: (Libpurple: msn) send IM {Comme t'es partie comme une voleuse sans rien dire!} to xxxxxxx@hotmail.com 12:30:14: (Libpurple: msn) prepare to send offline Message 12:30:14: (Libpurple: msn) Sending OIM: Comme t'es partie comme une voleuse sans rien dire! 12:30:14: (Libpurple: msn) No lock key challenge, waiting for SOAP Fault and Resend 12:30:14: (Libpurple: msn) Encoding OIM Message... 12:30:14: (Libpurple: msn) Encoded base64 body:{Q29tbWUgdCdlcyBwYXJ0aWUgY29tbWUgdW5lIHZvbGV1c2Ugc2FucyByaWVuIGRpcmUh}
Unless some other real error occurred later this is nothing to worry about. Did it report an error to you?
Re: UNOFFICIAL Adium with msnp15 testing
Ah I see now. It's a bug with the new reencoding function for oims. I did the build really really late and didn't test that since I thought it would work. Well I'll have to do another build then today it seems. 
Re: UNOFFICIAL Adium with msnp15 testing
Sorry i forgot to mention that it crash after this error.Dimmuxx wrote:You always get a SOAP fault the first time you send an OIM after logging in this is because you don't have the lock key yet. This doesn't matter though since it just resends the message again and the next time you send an OIM you will have the lock key unless it's expired in which case the resending happens again.neckaros wrote:I have a new bug with the last build when trying to send an offline message (i keep the original message so you can see it's size. Here is the debug log:Code: Select all
12:30:14: (Libpurple: msn) send IM {Comme t'es partie comme une voleuse sans rien dire!} to xxxxxxx@hotmail.com 12:30:14: (Libpurple: msn) prepare to send offline Message 12:30:14: (Libpurple: msn) Sending OIM: Comme t'es partie comme une voleuse sans rien dire! 12:30:14: (Libpurple: msn) No lock key challenge, waiting for SOAP Fault and Resend 12:30:14: (Libpurple: msn) Encoding OIM Message... 12:30:14: (Libpurple: msn) Encoded base64 body:{Q29tbWUgdCdlcyBwYXJ0aWUgY29tbWUgdW5lIHZvbGV1c2Ugc2FucyByaWVuIGRpcmUh}
Unless some other real error occurred later this is nothing to worry about. Did it report an error to you?
Thank you for the quick answear i will be waiting for the fix
Re: UNOFFICIAL Adium with msnp15 testing
Build 24342 is now updated and OIMs work! It's so late that I just updated the libpurple part and this will probably be my last build until Adium 1.3 is final. Since Adium 1.3 won't have msnp15 I will make a build with it. 
MD5 for the new build is e2dbe98608a86380630e57f750faefa0 so be sure that you use that one!
MD5 for the new build is e2dbe98608a86380630e57f750faefa0 so be sure that you use that one!
-
hippy dave
- Muffin
- Posts: 49
- Joined: Wed Sep 12, 2007 2:49 am
Re: UNOFFICIAL Adium with msnp15 testing
thanks as always 