unsuspend ~vishnuvishnu.2012

Hrm. I wonder if we have a funky bug here.
I can see the account - the usual grey screen of suspended.
BUT! The admin account page shows that the account is active.
https://launchpad.net/~vishnuvishnu.2012/+reviewaccount

I've just cycled the account thru suspended and back to active. Is now saying "The user is reactivated. He must use the "forgot password" to log in." But is still showing as a grey suspended account.

He is not greyed out because he is suspended. Launchpad does not use
account to manage people, SSO does. Launchpad uses email address. He
does not have an active email address, that is why he is greyed out. The
forgot password page will reset his password in SSO and log him into Lp.
The login process provides the preferred email address.

If login does not fix the email address, there is a new bug in Launchpad
foundations. There is a cluster of authentication bugs. We know the
authentication is not renaming deactivated account. We know that
authentication is moving email addresses and leaving users without
preferred email address. I have not seen an issue where a reactivated
account is not restored after authentication.

Not sure what you're actually asking us to do here?

* user has an active login.u.c account (#4129011 fwiw)
* has a different email on login.u.c - is a yahoo one, to LP, which is a gmail one
* has an active account on LP

Possibly made more complex by there being what looks to be another 3-4 accounts in login.u.c that the same person also has some access too. Looks quite similar to the bug we've had with internal staff having mixed access because of clashing login.u.c accounts. ie LP is associating to the wrong login.u.c account.

???

Gary, Stuart.

Do either of you know how to go about fixing this user's profile? The person needs his email address back and maybe openid data too?

On Thu, 2010-11-25 at 16:52 +0000, Vishnu G wrote:
> Thanks for the efforts you have taken..
> But since your efforts are useless..
> Error ID - 1790C1468
> This is the error ID when i tried to login after i have changed my
> password also..
> I can provide my email's password as it seems a new bug in lp.
> I wanna join your launchpad registry as it seems very nice..
> But my account is still not accessible...
> I belive in you and my password is "XXXXXXXXX".

Launchpad does not control passwords or accounts, That is the domain of
login.ubuntu.com. I have been tracking this issue at
https://answers.launchpad.net/launchpad-foundations/+question/134008
I understand the issue is that the efforts to reset that password and
login are causing a mismatch between your SSO identity and Lp profile.
This issue is escalated to the team that integrate login with Launchpad.

--
__Curtis C. Hovey_________
http://launchpad.net/

On Mon, 2010-11-29 at 09:28 +0000, Vishnu G wrote:
> I had successfully recovered my Lunchpad account by merging the
> account with my alternative account...
> Anyway thanks for your efforts...
...

Your Launchpad profiles are not merged:
    https://launchpad.net/~vish
    https://launchpad.net/~vishnu-201216

These are both active profiles with separate email addresses.

> How to get a mail ID with Ubuntu domain..
> The Ubuntu members group has been a closed group to join..

I do not know a lot about how Ubuntu scrapes Lp to setup an Ubuntu email
address.

I suggest that you really merge the profile you cannot login into the
profile you can login as. That will transfer the email addresses. Rename
the remaining profile if it does not have the name you want. I think the
Ubuntu email address will be fixed after a few days. You have a lot of
data in the vish account. I expect the merge page to time out often --
continue to reload the page until you see the message that merge was
successful.

--
__Curtis C. Hovey_________
http://launchpad.net/

Curtis, I'm not sure who this is directed at. Are you asking us to do that, or the user himself?

Vish contacted me. He created a new profile, merged the broken profile, then renamed the new one to the old one. He found his own solution to the suspend-openid debacle.