On Tue, 16 Feb 2021 18:38:42 +0100 Maximilian Stein <m...@steiny.biz> wrote:
This is weird, it still fails for me. I tested on two independent instances both using gitlab 13.6.7-1~fto10+1 and ruby-attr-encrypted 3.1.0-3~bpo10+1. I tested with a user with activated and with deactivated 2FA. In all cases, accessing "-/profile/two_factor_auth" failed with error 500.
From what I remember of your interventions in other bug reports, you tend to favour the packages versions from buster-backports? Here I try to minimise the use of buster-backports in favour of regular buster versions as much as possible, so the differences between our instances might be on this front. Registrations are open on my instance, that can be found at forge.my-email-domain Feel free to open an account there for testing purposes, as I am not a user of 2FA I might have missed something in my quick test. If the bug end up happening only on your instances and not on mine, we might find what triggers it by comparing `dpkg -l | grep ^ii` output and being careful about differences in packages versions.
OpenPGP_signature
Description: OpenPGP digital signature
