This is expected behavior if the recovery email address was not set in the user data LW2 imported from LW1 back in September, or whatever—LW2 simply doesn’t know about that email address at the moment! The LW2 devs have promised a “final import” of LW1 data, which should fix this sort of issue
I have set my recovery email four months ago (2017/11/14).
So it seems that I have to wait until I’ve been locked out of lw1.0 and only then I can try if I can log into lw2.0. If anything goes wrong (as it usually does with computer systems), I’ll be locked out of both and so I’ll be unable to communicate to the developers what went wrong. I shouldn’t have to say that this is highly undesirable—users should be able to test the new system before the old system is shut down.
BTW—are you sure that you can’t update software on that GNU/Linux computer?
Updating firefox seems to require (after several layers of depencies) updating udev—which requires updating kernel or it will might make the system unbootable. There are also circular depencies, changes needed to masked packages and manual configuration changes. At this point I’d need to back up my system, get a boot disk and prepare for significant donwtime. Additionaly updating firefox breaks many of the extensions that I’m using.
I might have the same problem—I managed to log in with my lw1 password, but failed to update the password.
(The user interface for changing password is confusing so I’m not sure if I’m following the correct procedure.)
Originally the “EMAIL” field in “Edit Account”-page was empty (even I had set the recovery email before the lw1 was shut down) and clicking the “RESET PASSWORD” caused popup “Must pass options.email”. I set the “EMAIL” field and pressed the SUBMIT-button. After that clicking the “RESET PASSWORD” in “Edit Account”-page caused popup “User not found” to appear. (Nothing appears in browser console.)
Trying to log in to greaterwrong with the lw1 password caused message “LessWrong 1.0 detected, legacy password salt attached” to appear and the Username and Password fields to be erased. Trying to log in again produced the same result. Trying to use greaterwrong’s reset password feature gave the same “User not found”-error.