Comment 28 for bug 243722

Which aMSN version is Dapper using? It might be a version running
MSNP9 instead of MSNP12, so you would normally have to change it in
the patch - after it is applied.

I am on holidays right now and this PC is not mine, so the number of
things I can install is very limited. However, I can probably tell
the problem if you give me the part of protocol.tcl that got patched,
and a dump of the status log (available through Ctrl+S from aMSN's
main window) and of the protocol log (Ctrl+D).

Vivia

On Wed, Aug 6, 2008 at 8:20 PM, Adrien Cunin <email address hidden> wrote:
> No luck with dapper. First the patch didn't apply correctly, and then it
> doesn't fix the bug it seems. So I'm closing as won't fix. If someone
> has a fixed package for dapper that works though, feel free to propose a
> debdiff.
>
> ** Changed in: amsn (Ubuntu Feisty)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Adrien Cunin (adri2000)
> Status: New => In Progress
>
> ** Changed in: amsn (Ubuntu Dapper)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Adrien Cunin (adri2000)
> Status: New => Won't Fix
>
> --
> amsn 0.97: login doesn't work anymore due to a protocol change
> https://bugs.launchpad.net/bugs/243722
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>