Nick saving in amsn 0.98.1

[José Cabo]

Binary package hint: amsn

Hi,

I'm has a fresh install of Ubuntu 9.10 Karmic with amsn 0.98.1 from ubuntu reps.

To reproduce:
- You need a passport/hotmail account.
- Loggin in amsn.
- Change your nick. (maybe you see your yourmail@yourmail).
- Go to Re-do your thing.
- Return to your amsn window.
- See that your nick is yourmail@yourmail again.

To resolve: update to the amsn 0.98.2

My Question informing of the 0.98.2 release: https://answers.launchpad.net/ubuntu/+source/amsn/+question/92078

[Steffan Jacobs (steffanjacobs)]

I am also affected by this bug, and have therefore confirmed it.
I have a few questioned just to clear this up though:
-What do you mean by redo your thing, close amsn and login again? That is what causes this for me.
-Where did you find 0.98.2? It is not on http://www.amsn-project.net/ . 0.98.1 is still the latest version there.

If there is a fix available upstream though, it might be usable in Ubuntu to solve this problem.

[Steffan Jacobs (steffanjacobs)]

I have added the related bug in SourceForge.

[José Cabo (folcwine)]

Hi Steffan Jacobs. The amsn 0.98.2 is in the amsn reps in launchpad. You can to make candidate the amsn 0.98.2?

Thanks Steffan Jacobs

[Steffan Jacobs (steffanjacobs)]

First of all, I have not authority to decide anything if that's what you mean.

I'm also pretty new to all this and I may be wrong about anything, I want to point out a few things however:

1) There is no current amsn 0.98.2 available on amsn's website and the only ones who can release it are the amsn team, by placing it on there website. There is nothing anyone can do on launchpad to make this happen.
2) Updates to stable Ubuntu releases aren't usually new upstream versions of package, they are based upon patches for a specific problem. This way you can prevent new problems from arising from other changes / new features.
3) This problem if complicated and based upon a problem in Microsofts servers, not amsn. A fix was committed somewhere, but from what I can see from the discussion, it is not really a stable fix yet and might be bandwidth hog. ( though I'd love for someone to prove me wrong on this!)

Read http://www.amsn-project.net/forums/viewtopic.php?t=7433 for example, though there may be a better thread about it.

[Steffan Jacobs (steffanjacobs)]

As far as I saw lately this bug is no longer applicable. As I did not change anything in my amsn, this is probably because Microsoft fixed its servers. I am therefore marking this bug as invalid, if anyone is still experiencing this problem, please change it back.