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.
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 …
Good catch. It would make sense to keep some version of LW1.0 running for a while even after the “final import” is done, purely for the sake of supporting existing users in migrating to LW2. However, I understand that the reddit-derived LW1 code is practically unmaintained by now, so Trike (the folks who host LW1) aren’t willing to keep it going for much longer. This means that the site devs’ hands are somewhat tied at this point and the status quo is not really tenable.
Updating firefox seems to require (after several layers of depencies) updating udev—which requires updating kernel or it will might make the system unbootable.
Kernel updates are relatively foolproof, unless you did something fancy like compiling a patched version with support for some sort of custom hardware. And you can probably install a newer version alongside the old, without updating udev, so you can get a choice at boot and have a way to ensure that the new version works before you make your system reliant on it. Even if you can’t in fact do this (because the newer kernels turn out to be incompatible with some feature of the existing system, like old udev), all you really need is a “live” boot disk to make sure that your hardware plays nice with the new kernel—everything else should be recoverable.
BTW, it’s only the very latest versions of Firefox that break all old-style addons. IIRC, 52esr still supports them and is relatively current.
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.
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.
Good catch. It would make sense to keep some version of LW1.0 running for a while even after the “final import” is done, purely for the sake of supporting existing users in migrating to LW2. However, I understand that the reddit-derived LW1 code is practically unmaintained by now, so Trike (the folks who host LW1) aren’t willing to keep it going for much longer. This means that the site devs’ hands are somewhat tied at this point and the status quo is not really tenable.
Kernel updates are relatively foolproof, unless you did something fancy like compiling a patched version with support for some sort of custom hardware. And you can probably install a newer version alongside the old, without updating udev, so you can get a choice at boot and have a way to ensure that the new version works before you make your system reliant on it. Even if you can’t in fact do this (because the newer kernels turn out to be incompatible with some feature of the existing system, like old udev), all you really need is a “live” boot disk to make sure that your hardware plays nice with the new kernel—everything else should be recoverable.
BTW, it’s only the very latest versions of Firefox that break all old-style addons. IIRC, 52esr still supports them and is relatively current.
I don’t think there is anything stopping you from trying to create a test LW2 account to see if you will be locked out